Triple
T27782774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill Valley Telegraph |
E699376
|
entity |
| Predicate | hasMastheadElement |
P46191
|
FINISHED |
| Object | nameplate reading “Hill Valley Telegraph” |
—
|
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: nameplate reading “Hill Valley Telegraph” | Statement: [Hill Valley Telegraph, hasMastheadElement, nameplate reading “Hill Valley Telegraph”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMastheadElement Context triple: [Hill Valley Telegraph, hasMastheadElement, nameplate reading “Hill Valley Telegraph”]
-
A.
hasMastheadFeature
Indicates that one entity is highlighted or featured in the masthead section of another entity (such as a page, site, or publication).
-
B.
hasHeading
chosen
Indicates that one entity serves as a heading or title for another entity.
-
C.
hasMast
Indicates that an object possesses or is equipped with a mast as part of its structure.
-
D.
hasMainElements
Indicates that something possesses or is composed of its primary or most important constituent parts.
-
E.
hasMainSectionStyle
Indicates that an entity is associated with a primary or dominant style used for its main section or main content area.
- 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_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: April 27, 2026, 5:11 p.m.