Triple
T29485913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Bennett (Ted character) |
E747919
|
entity |
| Predicate | birthYearInCanon |
P78440
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [John Bennett (Ted character), birthYearInCanon, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthYearInCanon Context triple: [John Bennett (Ted character), birthYearInCanon, 1977]
-
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.
launchedInFictionalYear
Indicates that an entity is depicted as being launched in a specified fictional or imaginary year within a narrative or fictional universe.
-
C.
eraInCanon
Indicates that a subject belongs to, occurs within, or is classified as part of a specific era defined in a canon or fictional continuity.
-
D.
characterCreatedInYear
Indicates the specific calendar year in which a fictional or narrative character was first created or introduced.
-
E.
releaseYearInFiction
Indicates the year in which a fictional work is depicted as being released or taking place within its narrative universe.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c05947c8190b34739a0a7c0201f |
completed | May 2, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:08 p.m.