Triple
T17473164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poquoson |
E425469
|
entity |
| Predicate | seafoodFestivalFocus |
P44899
|
FINISHED |
| Object | local seafood and maritime culture |
—
|
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: local seafood and maritime culture | Statement: [Poquoson, seafoodFestivalFocus, local seafood and maritime culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seafoodFestivalFocus Context triple: [Poquoson, seafoodFestivalFocus, local seafood and maritime culture]
-
A.
seafoodSpecialty
Indicates that one entity specializes in preparing, serving, or producing seafood as a primary focus or notable expertise.
-
B.
festivalFocus
chosen
Indicates that a festival is centered around, dedicated to, or thematically focused on a particular subject, activity, or feature.
-
C.
typeOfFoodFestival
Indicates the specific kind or category of food festival associated with an event or entity.
-
D.
festivalAttracts
Indicates that a festival draws or brings in attendees, participants, or interest toward itself.
-
E.
festivalFeature
Indicates that a festival includes or showcases a particular element, activity, or attraction as one of its features.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451b990848190b2e8510d67e94b79 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.