Triple
T6046563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Marlin Open |
E134679
|
entity |
| Predicate | typicalStartPort |
P68394
|
FINISHED |
| Object | Ocean City marinas |
—
|
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: Ocean City marinas | Statement: [White Marlin Open, typicalStartPort, Ocean City marinas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStartPort Context triple: [White Marlin Open, typicalStartPort, Ocean City marinas]
-
A.
typicalPort
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
B.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
C.
typicalStartSeason
Indicates the season during which something (such as an activity, event, or phenomenon) usually begins.
-
D.
defaultPort
Indicates that one entity serves as the standard or preconfigured communication port used by another entity unless explicitly overridden.
-
E.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
- F. None of above. chosen
Provenance (4 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056e53f508190864be04bc016c525 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049eb52a08190ac10fd703735f5aa |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:09 p.m.