Triple
T20030153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MARTA heavy rail cars |
E495099
|
entity |
| Predicate | usesCurrentCollectionMethod |
P138433
|
FINISHED |
| Object | third rail |
—
|
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: third rail | Statement: [MARTA heavy rail cars, usesCurrentCollectionMethod, third rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCurrentCollectionMethod Context triple: [MARTA heavy rail cars, usesCurrentCollectionMethod, third rail]
-
A.
currentCollectionMethod
Indicates the method or process currently being used to collect something (such as data, payments, or materials) from an entity.
-
B.
usesCollectionFor
Indicates that one entity employs or relies on a particular collection as a resource, tool, or context to perform its function or achieve a purpose.
-
C.
usesMethods
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
-
D.
currentCollection
Indicates that an entity is the presently active or selected collection associated with another entity or context.
-
E.
usesScanningMethod
Indicates that an entity performs or carries out an action by employing a specific scanning method.
- F. None of above. chosen
Provenance (4 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66291a00c8190b0b895909f32d623 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:36 p.m.