Triple
T1742238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Promontory Summit, Utah Territory |
E38257
|
entity |
| Predicate | hasReplicaFeature |
P16046
|
FINISHED |
| Object | replica steam locomotives |
—
|
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: replica steam locomotives | Statement: [Promontory Summit, Utah Territory, hasReplicaFeature, replica steam locomotives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReplicaFeature Context triple: [Promontory Summit, Utah Territory, hasReplicaFeature, replica steam locomotives]
-
A.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasReplicaDisplays
chosen
Indicates that an entity features or presents one or more replica items as displays.
-
C.
hasFeatureID
Indicates that an entity is associated with a specific feature identified by a unique ID.
-
D.
supportsDataReplicationFactor
Indicates that an entity enables, configures, or is compatible with a specified data replication factor for storing or duplicating data.
-
E.
hasDistinctFeature
Indicates that an entity possesses a specific characteristic or attribute that differentiates it from others.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.