Triple
T35479182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanamaker Grand Court Organ |
E1025421
|
entity |
| Predicate | hasConsoleLocation |
P207001
|
FINISHED |
| Object | balcony overlooking the Grand Court |
—
|
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: balcony overlooking the Grand Court | Statement: [Wanamaker Grand Court Organ, hasConsoleLocation, balcony overlooking the Grand Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConsoleLocation Context triple: [Wanamaker Grand Court Organ, hasConsoleLocation, balcony overlooking the Grand Court]
-
A.
hasProgramLocation
Indicates that a program, event, or activity takes place at or is associated with a specific location.
-
B.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
C.
hasStageLocation
Indicates that an event, process, or staged activity occurs at or is associated with a specific location.
-
D.
hasScreenLocation
Indicates that an entity is associated with a specific position or region on a screen or display surface.
-
E.
terminalLocation
Indicates the specific terminal or endpoint location associated with an entity or process.
- F. None of above. chosen
Provenance (4 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.