Triple
T27091611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Coast Borax Company |
E686181
|
entity |
| Predicate | usedTransportationMethod |
P11571
|
FINISHED |
| Object | 20-mule team wagon trains |
—
|
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: 20-mule team wagon trains | Statement: [Pacific Coast Borax Company, usedTransportationMethod, 20-mule team wagon trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTransportationMethod Context triple: [Pacific Coast Borax Company, usedTransportationMethod, 20-mule team wagon trains]
-
A.
usedTransportationMode
Indicates that an entity traveled or moved using a specified mode of transportation.
-
B.
passesUsedForTransportation
Indicates that the passes are utilized as a means or instrument for transporting people or goods.
-
C.
hasPrimaryTransportationMode
Indicates the main or most frequently used mode of transportation associated with an entity.
-
D.
hasPublicTransportUsage
Indicates that an entity makes use of, or is associated with the use of, public transportation services.
-
E.
usesTransport
chosen
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 8:41 a.m.