Triple
T23491497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boot Key Harbor |
E570686
|
entity |
| Predicate | hasApproximateMooringCount |
P76629
|
FINISHED |
| Object | 200+ |
—
|
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: 200+ | Statement: [Boot Key Harbor, hasApproximateMooringCount, 200+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateMooringCount Context triple: [Boot Key Harbor, hasApproximateMooringCount, 200+]
-
A.
hasBoatMoorings
chosen
Indicates that one entity provides or contains designated places where boats can be tied up or secured.
-
B.
mooringType
Indicates the specific method or system by which a vessel or floating structure is secured in place.
-
C.
numberOfBerths
Indicates the quantity of berths (sleeping places or docking spaces) associated with an entity.
-
D.
mooredAt
Indicates that one object, typically a vessel or floating structure, is secured or anchored at a specific location or facility.
-
E.
hasBerths
Indicates that one entity provides or contains sleeping or docking berths for another 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dc631c819099027e3a1c755a66 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:04 p.m.