Triple
T23652827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newport to Ensenada International Yacht Race |
E584212
|
entity |
| Predicate | startHarbor |
P125305
|
FINISHED |
| Object | Newport Harbor |
—
|
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: Newport Harbor | Statement: [Newport to Ensenada International Yacht Race, startHarbor, Newport Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startHarbor Context triple: [Newport to Ensenada International Yacht Race, startHarbor, Newport Harbor]
-
A.
startHarbour
chosen
Indicates that an entity serves as the starting harbor or port of departure for a journey or route.
-
B.
harbor
Indicates providing shelter, protection, or refuge for someone or something, often by keeping them in a safe or hidden place.
-
C.
harborDescription
Indicates that one entity serves as a harbor or safe anchorage location for another entity, typically providing shelter, docking, or protection.
-
D.
harborRole
Indicates that an entity serves in a particular capacity, function, or role within a specified context or relationship.
-
E.
harborManagedBy
Indicates that the operation, administration, or oversight of a harbor is carried out by a specified managing entity.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b3599128819092b6a44779889a78 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.