Triple
T5044849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Convent |
E113636
|
entity |
| Predicate | architecturalTypeInFiction |
P58551
|
FINISHED |
| Object | large house-like complex |
—
|
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 house-like complex | Statement: [the Convent, architecturalTypeInFiction, large house-like complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalTypeInFiction Context triple: [the Convent, architecturalTypeInFiction, large house-like complex]
-
A.
fictionalBuilding
chosen
Indicates that a building is imaginary or exists only within a fictional or invented context.
-
B.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
C.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
D.
architecturalUse
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
-
E.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fd81788190b7799f519277119a |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.