Triple
T14149309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benjamin Holladay |
E350631
|
entity |
| Predicate | usedTransportationMode |
P113005
|
FINISHED |
| Object | stagecoach |
—
|
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: stagecoach | Statement: [Benjamin Holladay, usedTransportationMode, stagecoach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTransportationMode Context triple: [Benjamin Holladay, usedTransportationMode, stagecoach]
-
A.
hasPrimaryTransportationMode
Indicates the main or most frequently used mode of transportation associated with an entity.
-
B.
passesUsedForTransportation
Indicates that the passes are utilized as a means or instrument for transporting people or goods.
-
C.
transportModeImportant
Indicates that the mode of transport used is considered significant or plays an important role in the context of the relationship or action.
-
D.
hasSecondaryTransportationMode
Indicates that an entity is associated with an additional, non-primary mode of transportation it can use or provide.
-
E.
hasPublicTransportUsage
Indicates that an entity makes use of, or is associated with the use of, public transportation services.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61237ef481909374c1f68a2370b7 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 12:55 a.m.