Triple
T27888620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hive Metastore |
E705292
|
entity |
| Predicate | commonlyBackedBy |
P183490
|
FINISHED |
| Object | MySQL |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: MySQL | Statement: [Hive Metastore, commonlyBackedBy, MySQL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyBackedBy Context triple: [Hive Metastore, commonlyBackedBy, MySQL]
-
A.
backedFor
Indicates that one entity provides support, endorsement, or backing for another entity, often in a financial, political, or strategic context.
-
B.
canBeBackedBy
Indicates that one entity is capable of being supported, guaranteed, or secured by another entity.
-
C.
backing
Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
-
D.
endorsedBy
Indicates that one entity has given formal approval, support, or recommendation to another entity.
-
E.
commonlyFrontedBy
Indicates that one element is typically placed at the beginning or in the leading position of another element.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: April 27, 2026, 6:34 p.m.