Triple
T9702823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argo |
E234819
|
entity |
| Predicate | hasVoyage |
P64755
|
FINISHED |
| Object | expedition to Colchis |
—
|
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: expedition to Colchis | Statement: [Argo, hasVoyage, expedition to Colchis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVoyage Context triple: [Argo, hasVoyage, expedition to Colchis]
-
A.
hasSeaVoyage
chosen
Indicates that an entity undertakes, includes, or is associated with a journey or travel conducted by sea.
-
B.
voyageOn
Indicates that an entity is traveling or being transported aboard a particular vessel or means of sea (or space) travel.
-
C.
voyageWith
Indicates that two or more entities travel together on the same journey or trip, sharing a common route or voyage.
-
D.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
E.
hasVessel
Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d7283188190bd50e18f643ad0d3 |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:18 p.m.