Triple
T2753568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tri-State Oversight Committee |
E61045
|
entity |
| Predicate | replacedFunction |
P5925
|
FINISHED |
| Object | state safety oversight for WMATA Metrorail |
—
|
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: state safety oversight for WMATA Metrorail | Statement: [Tri-State Oversight Committee, replacedFunction, state safety oversight for WMATA Metrorail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedFunction Context triple: [Tri-State Oversight Committee, replacedFunction, state safety oversight for WMATA Metrorail]
-
A.
formerFunction
chosen
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
B.
replacedClass
Indicates that one class has been superseded or substituted by another class, typically in a versioning or refactoring context.
-
C.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
D.
replacedInterface
Indicates that one interface has been substituted or superseded by another interface.
-
E.
replacedScript
Indicates that one script has been substituted for or superseded by another script.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb6ed9c08190824d1866e198ef80 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.