Triple
T36172741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cowes–Dinard–St Malo Race |
E1046188
|
entity |
| Predicate | hasFinishPort |
P200931
|
FINISHED |
| Object | Port of Saint-Malo |
—
|
NE NERFINISHED |
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: Port of Saint-Malo | Statement: [Cowes–Dinard–St Malo Race, hasFinishPort, Port of Saint-Malo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinishPort Context triple: [Cowes–Dinard–St Malo Race, hasFinishPort, Port of Saint-Malo]
-
A.
hasFrameFinish
Indicates that an entity’s frame possesses a specific surface treatment or finish.
-
B.
hasCommonFinish
Indicates that two or more entities share the same type or style of finish (e.g., surface treatment, coating, or final appearance).
-
C.
hasPorts
Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
-
D.
hasFinalState
Indicates that an entity ultimately results in, transitions to, or ends in a specified final state or condition.
-
E.
hasPortTerminalAt
chosen
Indicates that an entity possesses or operates a port terminal located at a specified place.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:08 p.m.