Triple
T4260239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Fur Company |
E96084
|
entity |
| Predicate | usedTransportMethod |
P11571
|
FINISHED |
| Object | canoes |
—
|
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: canoes | Statement: [American Fur Company, usedTransportMethod, canoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTransportMethod Context triple: [American Fur Company, usedTransportMethod, canoes]
-
A.
usesTransport
chosen
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
B.
usesTransportBrand
Indicates that one entity makes use of a transportation service, vehicle, or system associated with a specific brand.
-
C.
usedCross
Indicates that one entity made use of a cross-shaped object or structure, or traversed by means of a crossing point such as a crosswalk or intersection.
-
D.
replacedModeOfTransport
Indicates that one mode of transport has been substituted or superseded by another in fulfilling a given travel or transport function.
-
E.
usedMedium
Indicates that an action or communication was carried out through a particular medium or channel.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34f8103b48190934a810faafa6cb7 |
completed | March 12, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.