Triple
T32973554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Zephyr |
E843591
|
entity |
| Predicate | previousAreaName |
P114670
|
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: [Golden Zephyr, previousAreaName, Paradise Pier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAreaName Context triple: [Golden Zephyr, previousAreaName, Paradise Pier]
-
A.
previousLocationName
Indicates that one entity specifies the name of a location where another entity was situated or occurred before its current location.
-
B.
formerNameOfAreaWithin
Indicates that one area previously had a different name while remaining within the same larger encompassing area.
-
C.
predecessorArea
chosen
Indicates that one area previously existed or was defined before another area in a sequence or versioning of areas.
-
D.
hasAreaName
Indicates that an entity is associated with a specific named geographic or administrative area.
-
E.
previousBorough
Indicates that one borough directly precedes another in a defined ordering or sequence.
- 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_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 1, 2026, 1:22 a.m.