Triple
T1739923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IND Culver Line (subway portion) |
E38208
|
entity |
| Predicate | usesPowerCollection |
P14641
|
FINISHED |
| Object | contact shoe |
—
|
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 shoe | Statement: [IND Culver Line (subway portion), usesPowerCollection, contact shoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPowerCollection Context triple: [IND Culver Line (subway portion), usesPowerCollection, contact shoe]
-
A.
powerCollectionMethod
chosen
Indicates the method or process by which power is collected, harvested, or obtained in a given context.
-
B.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
hasNumberOfPowers
Indicates the quantity of distinct powers or abilities that an entity possesses.
-
D.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
E.
canCollect
Indicates that one entity has the ability or permission to gather, receive, or take possession of another entity.
- 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.