Triple
T7742065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Jones |
E175533
|
entity |
| Predicate | fictionalBirthYear |
P78440
|
FINISHED |
| Object | 1899 |
—
|
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: 1899 | Statement: [Indiana Jones, fictionalBirthYear, 1899]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalBirthYear Context triple: [Indiana Jones, fictionalBirthYear, 1899]
-
A.
fictionalBirthDate
Indicates the date on which a fictional character is stated or assumed to have been born within its narrative or canon.
-
B.
fictionalBirthStatus
Indicates the relationship between an entity and its status of being born or created within a fictional or imaginary context.
-
C.
foundedInFictionalYear
Indicates that an entity was established or created in a year that exists only within a fictional or imaginary timeline, rather than in real-world history.
-
D.
fictionalBirthPlace
Indicates the fictional location where a character or entity is described as having been born within a narrative or imagined context.
-
E.
fictionalAge
Indicates the age attributed to an entity within a fictional or narrative context, rather than its real-world age.
- 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_69c6995f9c60819092e386192bd63c6f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:07 p.m.