Triple
T11845253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiri trade voyages |
E281757
|
entity |
| Predicate | directionReturn |
P76664
|
FINISHED |
| Object | eastward back to Motu villages |
—
|
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: eastward back to Motu villages | Statement: [Hiri trade voyages, directionReturn, eastward back to Motu villages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionReturn Context triple: [Hiri trade voyages, directionReturn, eastward back to Motu villages]
-
A.
routeDirectionB
chosen
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
B.
directionRelativeTo
Indicates the spatial orientation of one entity in relation to another, such as which way it faces or points relative to a reference entity.
-
C.
routeDirectionA
Indicates the primary or first directional orientation or heading associated with a specific route.
-
D.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
E.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65b5ff08190bb58361f6a6acdca |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.