Triple
T5176764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venus |
E116817
|
entity |
| Predicate | divineAncestorOf |
P8000
|
FINISHED |
| Object | Roman people |
—
|
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: Roman people | Statement: [Venus, divineAncestorOf, Roman people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divineAncestorOf Context triple: [Venus, divineAncestorOf, Roman people]
-
A.
divineLineage
Indicates that one entity is descended from, or originates from, a divine or god-like being.
-
B.
hasParentDeity
Indicates that one deity is the parent (progenitor or creator) of another deity.
-
C.
hasMortalOrSemiDivineAncestry
Indicates that an entity descends from, or is otherwise ancestrally connected to, beings who are mortal or possess semi-divine (partly divine) status.
-
D.
foundingAncestor
chosen
Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
-
E.
divineFather
Indicates a paternal relationship in which one entity is regarded as the godly or divine father of another.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7974a5308190819b100e07189131 |
completed | March 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.