Triple
T7074762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William the Englishman |
E164787
|
entity |
| Predicate | architecturalTypeSpecialization |
P4631
|
FINISHED |
| Object | cathedral architecture |
—
|
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: cathedral architecture | Statement: [William the Englishman, architecturalTypeSpecialization, cathedral architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalTypeSpecialization Context triple: [William the Englishman, architecturalTypeSpecialization, cathedral architecture]
-
A.
architectureType
chosen
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
B.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
C.
architecturalUse
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
-
D.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
-
E.
architecturalPlanner
Indicates a relationship where an entity is responsible for designing, organizing, or planning the architectural structure or layout of another 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4ccb42c81909f5627aa97db7a84 |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:39 p.m.