Triple
T29311912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Hall |
E743256
|
entity |
| Predicate | architectNotedFor |
P179492
|
FINISHED |
| Object | work in the late 19th century |
—
|
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: work in the late 19th century | Statement: [South Hall, architectNotedFor, work in the late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectNotedFor Context triple: [South Hall, architectNotedFor, work in the late 19th century]
-
A.
architectIsNotableFor
Indicates that an architect is recognized or distinguished for a particular work, contribution, or achievement.
-
B.
coArchitectOf
Indicates a relationship where two or more entities jointly serve as architects of the same project, design, or structure.
-
C.
architectOfStructure
Indicates that an entity is the designer or creator responsible for the architectural design of a particular structure.
-
D.
majorFigureInArchitecture
Indicates that an entity is recognized as a leading or highly influential figure within the field of architecture.
-
E.
hasCountryArchitect
Indicates that an entity has an architect associated with a specific country.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 28, 2026, 1:17 p.m.