Triple
T22123468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Phantom of the Range |
E546731
|
entity |
| Predicate | workOriginPeriod |
P63537
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [The Phantom of the Range, workOriginPeriod, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workOriginPeriod Context triple: [The Phantom of the Range, workOriginPeriod, early 20th century]
-
A.
timePeriodOrigin
Indicates that one entity is the time period in which the other entity originated or first came into existence.
-
B.
workOriginYear
Indicates the year in which a work (such as a creative, scholarly, or artistic piece) was originally created or first produced.
-
C.
periodOfOriginOfSourceWork
chosen
Indicates the historical time period during which the original source work was created or first came into existence.
-
D.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
E.
partOfWorkPeriod
Indicates that a specific time span is contained within, and belongs to, a larger defined work period.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1297f3fb48190b6aaca18b40c37ab |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.