Triple
T27656980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Mermaid |
E697020
|
entity |
| Predicate | locationOfRole |
P76778
|
FINISHED |
| Object | Coney Island Boardwalk |
—
|
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: Coney Island Boardwalk | Statement: [Queen Mermaid, locationOfRole, Coney Island Boardwalk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfRole Context triple: [Queen Mermaid, locationOfRole, Coney Island Boardwalk]
-
A.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
B.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
C.
workLocationOfFictionalCharacter
chosen
Indicates the place or organization where a fictional character is depicted as working within their narrative context.
-
D.
locationInPlay
Indicates that an entity is currently situated or active within the defined play area or game environment.
-
E.
crewLocation
Indicates that a crew is located at, assigned to, or present in a specific place or environment.
- 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_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: April 27, 2026, 2:34 p.m.