Triple
T27782744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill Valley Telegraph |
E699376
|
entity |
| Predicate | frontPageHeadline |
P77500
|
FINISHED |
| Object | “Clock To Be Repaired” |
—
|
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: “Clock To Be Repaired” | Statement: [Hill Valley Telegraph, frontPageHeadline, “Clock To Be Repaired”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontPageHeadline Context triple: [Hill Valley Telegraph, frontPageHeadline, “Clock To Be Repaired”]
-
A.
headOfStoryOn
chosen
Indicates that one entity serves as the main headline or leading title for a story that appears on another entity (such as a page or section).
-
B.
newspaperTitle
Indicates the title or name by which a newspaper is identified.
-
C.
headlinedBy
Indicates that something (such as an event, show, or publication) is led, featured, or given top billing by a particular main performer, act, or entity.
-
D.
featuredIssue
Indicates that an issue is highlighted or given special prominence relative to other issues.
-
E.
currentHeadTitle
Indicates the official title or position currently held by the head or leader of an entity.
- 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_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 5:11 p.m.