Triple
T6453652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wey Navigation |
E139935
|
entity |
| Predicate | cargoHistoricallyCarried |
P31374
|
FINISHED |
| Object | timber |
—
|
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: timber | Statement: [Wey Navigation, cargoHistoricallyCarried, timber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoHistoricallyCarried Context triple: [Wey Navigation, cargoHistoricallyCarried, timber]
-
A.
hasTransportHistoryAs
Indicates that an entity has a record or log of being transported, characterized or classified in a specific way.
-
B.
railCarries
Indicates that a rail or railway system transports or conveys a specified entity from one place to another.
-
C.
hasTransportHistory
chosen
Indicates that there exists a record or sequence of past transportation-related events or movements associated with an entity.
-
D.
cargoAccess
Indicates that an entity has permission or capability to access, enter, or interact with a cargo area or cargo-related contents.
-
E.
historicallyStoredGoods
Indicates that an entity has previously stored certain goods at some time in the past.
- 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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069d1c7c481909df9d2369edf5e74 |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:47 p.m.