Triple
T13363127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naro Moru route |
E318868
|
entity |
| Predicate | usualDurationRoundTrip |
P7618
|
FINISHED |
| Object | 4 to 5 days |
—
|
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: 4 to 5 days | Statement: [Naro Moru route, usualDurationRoundTrip, 4 to 5 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usualDurationRoundTrip Context triple: [Naro Moru route, usualDurationRoundTrip, 4 to 5 days]
-
A.
numberOfDailyRoundTrips
Indicates the total count of round-trip journeys performed per day in the described context.
-
B.
voyageDuration
Indicates the length of time that a voyage or journey lasts from its start to its end.
-
C.
timeToTravelEndToEnd
Indicates the duration required to traverse from the starting point to the ending point of something (e.g., a route, path, or system) without interruption.
-
D.
typicalDurationDays
chosen
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
E.
travelTimeTypical
Indicates the usual or expected amount of time it takes to travel between two locations under normal conditions.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da628affd081909f1790d333f0eef4 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.