Triple
T35661698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of Castile and León |
E1030450
|
entity |
| Predicate | castleFeatures |
P89604
|
FINISHED |
| Object | three-towered castle |
—
|
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: three-towered castle | Statement: [coat of arms of Castile and León, castleFeatures, three-towered castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castleFeatures Context triple: [coat of arms of Castile and León, castleFeatures, three-towered castle]
-
A.
castle
Indicates that one entity is a castle associated with, located at, or serving as the stronghold or residence for another entity.
-
B.
castleBuilt
Indicates that a castle has been constructed or established, typically by a specific agent or during a particular time period.
-
C.
castleBuiltOf
Indicates that a castle is constructed primarily from a specified material.
-
D.
battlementFeature
Indicates that one architectural element functions as a defensive battlement or is a structural feature of a battlement.
-
E.
hasCastleFeature
chosen
Indicates that an entity possesses or includes a specific architectural or structural feature of a castle.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fa7d1708190bb5defe2ea54dc75 |
completed | May 3, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.