Triple
T660668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPP |
E11745
|
entity |
| Predicate | railroadReportingMarkStatus |
P12717
|
FINISHED |
| Object | active |
—
|
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: active | Statement: [UPP, railroadReportingMarkStatus, active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadReportingMarkStatus Context triple: [UPP, railroadReportingMarkStatus, active]
-
A.
historicalRecordStatus
Indicates the status or condition of a record within a historical or archival context (e.g., active, archived, revised, or obsolete).
-
B.
standardizationStatus
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
hasStatusLabel
chosen
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
E.
flagshipStatus
Indicates that an entity holds the primary or most prominent position within a group, organization, or collection, often serving as its leading or representative example.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d1406ec8190abf546549264c85d |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.