Triple
T20078213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris |
E499926
|
entity |
| Predicate | exposedAtBirthBecauseOf |
P138614
|
FINISHED |
| Object | prophecy of Troy’s destruction |
—
|
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: prophecy of Troy’s destruction | Statement: [Paris, exposedAtBirthBecauseOf, prophecy of Troy’s destruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposedAtBirthBecauseOf Context triple: [Paris, exposedAtBirthBecauseOf, prophecy of Troy’s destruction]
-
A.
gaveBirthAt
Indicates that one entity gave birth at a specific location or time associated with another entity.
-
B.
switchedAtBirthWith
Indicates that two individuals were mistakenly exchanged for each other at birth, so each was raised by the other’s biological family.
-
C.
birthType
Indicates the manner or method by which a birth occurred or was brought about.
-
D.
bornDuring
Indicates that an entity’s birth occurred within the temporal span of a specified event, period, or time interval.
-
E.
born
Indicates that an entity comes into existence at a specific time and place, typically from parent entities.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643e216c819088c002fc1de2772a |
completed | April 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:40 p.m.