Triple
T31876106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenlee |
E813744
|
entity |
| Predicate | voyageArea |
P84698
|
FINISHED |
| Object | global deep-sea routes |
—
|
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: global deep-sea routes | Statement: [Glenlee, voyageArea, global deep-sea routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voyageArea Context triple: [Glenlee, voyageArea, global deep-sea routes]
-
A.
voyagedNear
Indicates that one entity traveled by sea or space in close proximity to another entity or location.
-
B.
cruiseRegion
chosen
Indicates the geographic region or area in which a cruise operates or takes place.
-
C.
voyageOn
Indicates that an entity is traveling or being transported aboard a particular vessel or means of sea (or space) travel.
-
D.
nauticalRegion
Indicates that one entity is a maritime or nautical area within which the other entity is located, operates, or is relevant.
-
E.
voyageWith
Indicates that two or more entities travel together on the same journey or trip, sharing a common route or voyage.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0a50fcc8190b0b5ffc5f81daba9 |
completed | May 3, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:55 p.m.