Triple
T9616797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mediterranean Harbor |
E232238
|
entity |
| Predicate | containsShowVenue |
P81468
|
FINISHED |
| Object | harbor show lagoon |
—
|
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: harbor show lagoon | Statement: [Mediterranean Harbor, containsShowVenue, harbor show lagoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsShowVenue Context triple: [Mediterranean Harbor, containsShowVenue, harbor show lagoon]
-
A.
hasVenueIn
chosen
Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
-
B.
connectsToEventVenue
Indicates that one entity serves as a link or route providing access or connection to an event venue.
-
C.
hasVenueContext
Indicates that an entity is associated with a particular venue or setting that provides contextual information about where it occurs or is situated.
-
D.
hasPrincipalVenue
Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
-
E.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9aad71a0819084ea00c2409e9922 |
completed | April 1, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:09 p.m.