Triple
T34981328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dead City |
E1008821
|
entity |
| Predicate | firstEnglishTitleUsage |
P206779
|
FINISHED |
| Object | The Dead City |
E1008821
|
NE 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: The Dead City | Statement: [The Dead City, firstEnglishTitleUsage, The Dead City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEnglishTitleUsage Context triple: [The Dead City, firstEnglishTitleUsage, The Dead City]
-
A.
firstUseAsTitleDate
Indicates the date on which something was first used as a title.
-
B.
firstEnglishLanguageHitFor
Indicates that one entity is the earliest or primary occurrence of another entity in the context of English-language results or listings.
-
C.
firstUseAsTitleBy
Indicates that an entity is the first to use a given term, phrase, or designation as a formal title for another entity.
-
D.
firstProminentUse
Indicates the earliest notable or widely recognized instance in which something was used in a significant or influential way.
-
E.
firstHistoricalUse
Indicates that the subject entity represents the earliest known or recorded instance of the object entity being used or occurring in history.
- F. None of above. chosen
Provenance (5 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b27fc0dc8190b1c1976265e06314 |
completed | June 21, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.