Triple
T26917177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOSPR |
E677546
|
entity |
| Predicate | architectOfHall |
P85898
|
FINISHED |
| Object | Konior Studio |
—
|
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: Konior Studio | Statement: [NOSPR, architectOfHall, Konior Studio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectOfHall Context triple: [NOSPR, architectOfHall, Konior Studio]
-
A.
architectOfStructure
chosen
Indicates that an entity is the designer or creator responsible for the architectural design of a particular structure.
-
B.
architectOfCommissionedBuilding
Indicates that a person served as the architect responsible for designing a building that was specifically commissioned.
-
C.
architectOfArena
Indicates that one entity is the architect responsible for designing or planning the specified arena.
-
D.
architectOfMainBuilding
Indicates that one entity is the architect who designed the main building associated with another entity.
-
E.
mainHallDedicatedTo
Indicates that the primary hall of a building or complex is formally dedicated or devoted to a particular person, group, purpose, or 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 6:05 a.m.