Triple
T27888619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hive Metastore |
E705292
|
entity |
| Predicate | typicallyBackedBy |
P183490
|
FINISHED |
| Object | relational database |
—
|
LITERAL FINISHED |
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: relational database | Statement: [Hive Metastore, typicallyBackedBy, relational database]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyBackedBy Context triple: [Hive Metastore, typicallyBackedBy, relational database]
-
A.
commonlyBackedBy
chosen
Indicates that something is typically supported, endorsed, or funded by a particular party or group.
-
B.
backedFor
Indicates that one entity provides support, endorsement, or backing for another entity, often in a financial, political, or strategic context.
-
C.
typicallyOwnedBy
Indicates that something is most commonly or usually possessed or owned by a particular type of entity.
-
D.
canBeBackedBy
Indicates that one entity is capable of being supported, guaranteed, or secured by another entity.
-
E.
backedByMechanism
Indicates that something is supported, enabled, or made possible by an underlying mechanism or system.
- F. None of above.
Provenance (3 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_6a00372ff0e48190b3ed91f9bae9da6c |
completed | May 10, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_6a00359c1b8481909c1e43df9f5a789a |
completed | May 10, 2026, 7:37 a.m. |
Created at: April 27, 2026, 6:34 p.m.