Triple
T27782532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill Valley Clock Tower |
E699370
|
entity |
| Predicate | hasInUniverseCompletionYear |
P6114
|
FINISHED |
| Object | 1885 |
—
|
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: 1885 | Statement: [Hill Valley Clock Tower, hasInUniverseCompletionYear, 1885]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInUniverseCompletionYear Context triple: [Hill Valley Clock Tower, hasInUniverseCompletionYear, 1885]
-
A.
revisionCompletionYear
Indicates the year in which a revision of something (e.g., a work, document, or item) was completed.
-
B.
activeYearsInUniverse
Indicates the span of time during which an entity is active or present within a particular fictional universe or continuity.
-
C.
originalCompletionYear
chosen
Indicates the year in which something (such as a project, work, or construction) was first fully completed.
-
D.
hasInUniversePerformance
Indicates that an entity gives or participates in a performance that occurs within a particular fictional or defined universe.
-
E.
completedInDynasty
Indicates that an action, project, or work was finished during the period of a specified dynasty.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 27, 2026, 5:11 p.m.