Triple
T27868530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill Valley Courthouse Square |
E704426
|
entity |
| Predicate | fictionalFirstAppearanceYear |
P121574
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [Hill Valley Courthouse Square, fictionalFirstAppearanceYear, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalFirstAppearanceYear Context triple: [Hill Valley Courthouse Square, fictionalFirstAppearanceYear, 1985]
-
A.
firstPublicationYearOfAppearance
Indicates the year in which an entity (such as a work or character) first appeared in a published form.
-
B.
yearOfFirstApparition
chosen
Indicates the calendar year in which the entity first appeared or was introduced.
-
C.
releaseYearInFiction
Indicates the year in which a fictional work is depicted as being released or taking place within its narrative universe.
-
D.
launchedInFictionalYear
Indicates that an entity is depicted as being launched in a specified fictional or imaginary year within a narrative or fictional universe.
-
E.
fictionalBirthYear
Indicates the year in which a fictional character is stated or assumed to have been born within its narrative or canon.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 6:22 p.m.