Triple
T32973732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corn Dog Castle |
E843595
|
entity |
| Predicate | previouslyLocatedInArea |
P59728
|
FINISHED |
| Object | Paradise Pier |
—
|
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: Paradise Pier | Statement: [Corn Dog Castle, previouslyLocatedInArea, Paradise Pier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyLocatedInArea Context triple: [Corn Dog Castle, previouslyLocatedInArea, Paradise Pier]
-
A.
previouslyLocatedIn
chosen
Indicates that an entity was located in a particular place or region at some time in the past, but is not necessarily located there now.
-
B.
formerlyLocatedOn
Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
-
C.
previouslyOutside
Indicates that an entity was located outside a specified area or boundary at some earlier time prior to the current reference point.
-
D.
formerNameOfAreaWithin
Indicates that one area previously had a different name while remaining within the same larger encompassing area.
-
E.
locatedAtFormer
Indicates that an entity is currently located at a place where another entity was previously located.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
Created at: May 1, 2026, 1:22 a.m.