Triple
T4558926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Staircase landing |
E120546
|
entity |
| Predicate | isTypicallyFoundIn |
P9687
|
FINISHED |
| Object | large building |
—
|
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: large building | Statement: [Grand Staircase landing, isTypicallyFoundIn, large building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyFoundIn Context triple: [Grand Staircase landing, isTypicallyFoundIn, large building]
-
A.
commonlyFoundOn
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
-
B.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
C.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
D.
isHomeOf
Indicates that a place serves as the primary residence or base for a person, group, or organization.
-
E.
traditionallyFoundIn
Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd5829cc34819086ad2ae58446502e |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.