Triple
T22600943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vendée Globe |
E574812
|
entity |
| Predicate | typicalFleetSize |
P1848
|
FINISHED |
| Object | 20 to 30 boats depending on edition |
—
|
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: 20 to 30 boats depending on edition | Statement: [Vendée Globe, typicalFleetSize, 20 to 30 boats depending on edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFleetSize Context triple: [Vendée Globe, typicalFleetSize, 20 to 30 boats depending on edition]
-
A.
fleetSize
chosen
Indicates the total number of vehicles, vessels, or units that collectively make up a fleet associated with an entity.
-
B.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
C.
typicalGroupSize
Indicates the usual or characteristic number of individuals that typically form a group in this context.
-
D.
typicalTeamSize
Indicates the usual or most common number of members that make up a given team.
-
E.
relativeSizeInFleet
Indicates the comparative size or capacity of an entity relative to other entities within the same fleet.
- 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_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. |
Created at: April 17, 2026, 2:50 p.m.