Triple
T33961842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Andrew Undershaft |
E870735
|
entity |
| Predicate | standsAmid |
P190379
|
FINISHED |
| Object | modern skyscrapers |
—
|
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: modern skyscrapers | Statement: [St Andrew Undershaft, standsAmid, modern skyscrapers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standsAmid Context triple: [St Andrew Undershaft, standsAmid, modern skyscrapers]
-
A.
standsAt
Indicates that one entity is positioned upright at or near a specific location or reference point associated with another entity.
-
B.
standsUpTo
Indicates confronting, resisting, or opposing another entity’s actions, demands, or influence, especially in the face of pressure or intimidation.
-
C.
stoodIn
Indicates that one entity was physically located within and occupying a place or area defined by another entity while in a standing position.
-
D.
stands
Indicates that an entity is in an upright position, typically supported by its feet or base, rather than sitting, lying, or moving.
-
E.
standingBody
Indicates that a body is in an upright, standing posture rather than sitting, lying, or moving.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc4b5f22c8190b8b256adbdc2570c |
completed | May 7, 2026, 4:58 p.m. |
Created at: May 1, 2026, 1:50 a.m.