Triple
T8211262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradise Pier to Pixar Pier |
E191820
|
entity |
| Predicate | mainEntranceFeature |
P43549
|
FINISHED |
| Object | Pixar Pier marquee |
—
|
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: Pixar Pier marquee | Statement: [Paradise Pier to Pixar Pier, mainEntranceFeature, Pixar Pier marquee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEntranceFeature Context triple: [Paradise Pier to Pixar Pier, mainEntranceFeature, Pixar Pier marquee]
-
A.
mainEntranceOn
Indicates that the primary entrance of one entity is located on or faces toward another entity, such as a particular side, street, or boundary.
-
B.
hasLandmarkAtEntrance
chosen
Indicates that a specific landmark is located at or directly adjacent to the entrance of something.
-
C.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
D.
doorwayFeature
Indicates that one entity is a feature, characteristic, or structural element specifically associated with a doorway of another entity.
-
E.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dec42c819090252fe186a68d34 |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.