Triple
T7977573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George McFly |
E185483
|
entity |
| Predicate | yearOfFictionalBirth |
P78440
|
FINISHED |
| Object | 1938 |
—
|
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: 1938 | Statement: [George McFly, yearOfFictionalBirth, 1938]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfFictionalBirth Context triple: [George McFly, yearOfFictionalBirth, 1938]
-
A.
fictionalBirthYear
chosen
Indicates the year in which a fictional character is stated or assumed to have been born within its narrative or canon.
-
B.
fictionalBirthDate
Indicates the date on which a fictional character is stated or assumed to have been born within its narrative or canon.
-
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.
authorBirthYear
Indicates the year in which the author of a work or text was born.
-
E.
basedOnFictionalDateIn
Indicates that something is derived from, inspired by, or determined using a fictional date occurring within a specified work, timeline, or fictional context.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bf716508190b4245bd5d89ae8c4 |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:14 p.m.