Triple
T4381194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Hercules |
E99131
|
entity |
| Predicate | hasMooringFacilitiesFor |
P14974
|
FINISHED |
| Object | mega yachts |
—
|
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: mega yachts | Statement: [Port Hercules, hasMooringFacilitiesFor, mega yachts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMooringFacilitiesFor Context triple: [Port Hercules, hasMooringFacilitiesFor, mega yachts]
-
A.
mooredAt
Indicates that one object, typically a vessel or floating structure, is secured or anchored at a specific location or facility.
-
B.
berthingOrDockingTarget
chosen
Indicates that an entity serves as the location or structure where a vessel or vehicle is intended to berth or dock.
-
C.
hasBerths
Indicates that one entity provides or contains sleeping or docking berths for another entity.
-
D.
hasNearbyHarbor
Indicates that one location has a harbor situated close to it in geographic proximity.
-
E.
mooredInState
Indicates that an object such as a vessel or structure is secured or anchored within the territorial waters or jurisdiction of a specific state.
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35243036481909fb0a001c3cb1ff2 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.