Triple
T36158947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4-8-2 Mountain steam locomotives |
E1045817
|
entity |
| Predicate | hasEraOfUse |
P119523
|
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: [4-8-2 Mountain steam locomotives, hasEraOfUse, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEraOfUse Context triple: [4-8-2 Mountain steam locomotives, hasEraOfUse, early 20th century]
-
A.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
B.
usedDuringEraOf
chosen
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
-
C.
hasEraInfluence
Indicates that one era or time period has a significant impact on shaping the characteristics, developments, or outcomes of another.
-
D.
usedEraName
Indicates that an entity employed or referenced a specific historical or calendrical era name in its dating or designation.
-
E.
isBsideOfEra
Indicates that one entity is the B-side counterpart associated with a particular era of another entity (such as a primary release or 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.