Triple
T22600935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vendée Globe |
E574812
|
entity |
| Predicate | primaryNavigation |
P148892
|
FINISHED |
| Object | modern electronic navigation systems |
—
|
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: modern electronic navigation systems | Statement: [Vendée Globe, primaryNavigation, modern electronic navigation systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryNavigation Context triple: [Vendée Globe, primaryNavigation, modern electronic navigation systems]
-
A.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
B.
primarySection
Indicates that one entity is the main or most important section or subdivision associated with another entity.
-
C.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
D.
primaryRoutes
Indicates the main or most important routes that connect or serve between specified locations or entities.
-
E.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
- F. None of above. chosen
Provenance (4 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626c6ce08190b991e89b12c67a5a |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 2:50 p.m.