Triple
T20030190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MARTA heavy rail cars |
E495099
|
entity |
| Predicate | hasPowerCollection |
P138437
|
FINISHED |
| Object | contact shoes |
—
|
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: contact shoes | Statement: [MARTA heavy rail cars, hasPowerCollection, contact shoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerCollection Context triple: [MARTA heavy rail cars, hasPowerCollection, contact shoes]
-
A.
hasNumberOfPowers
Indicates the quantity of distinct powers or abilities that an entity possesses.
-
B.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
hasPowerBase
Indicates that an entity derives support, influence, or authority from a particular group, location, or resource that serves as its primary base of power.
-
D.
hasCorePower
Indicates that an entity possesses a primary or fundamental power, ability, or capability that defines its essential function or role.
-
E.
hadPowerType
Indicates that an entity possessed or was associated with a specific type or category of power.
- 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.