Triple
T14665982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hozu River |
E344373
|
entity |
| Predicate | transportTypeUsed |
P1379
|
FINISHED |
| Object | flat-bottomed boats |
—
|
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: flat-bottomed boats | Statement: [Hozu River, transportTypeUsed, flat-bottomed boats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportTypeUsed Context triple: [Hozu River, transportTypeUsed, flat-bottomed boats]
-
A.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
usedTransportationMode
Indicates that an entity traveled or moved using a specified mode of transportation.
-
C.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
D.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
-
E.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54c69f8819080a37161deecfba8 |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.