Triple
T27656921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Neptune |
E697019
|
entity |
| Predicate | titleInEvent |
P95183
|
FINISHED |
| Object | King of the Mermaid Parade |
—
|
NE NERFINISHED |
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: King of the Mermaid Parade | Statement: [King Neptune, titleInEvent, King of the Mermaid Parade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInEvent Context triple: [King Neptune, titleInEvent, King of the Mermaid Parade]
-
A.
mainEventTitle
Indicates the primary or official title assigned to an event within a given context.
-
B.
mainEventTitleOnTheLine
Indicates that the primary event’s title is being prominently featured or emphasized as the key focus (e.g., “on the line”) in a given context.
-
C.
titleChallengeEvent
Indicates an event in which a participant competes or acts to obtain, defend, or change a specific title or status.
-
D.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
E.
titleHeldByDuringEvent
chosen
Indicates that a specific title or position was held by a particular entity for the duration of a given event or time-bounded occurrence.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 27, 2026, 2:34 p.m.