Triple
T38690821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of the Crown of Castile |
E949255
|
entity |
| Predicate | institutionalAspect |
P191535
|
FINISHED |
| Object | Cortes of Castile |
—
|
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: Cortes of Castile | Statement: [History of the Crown of Castile, institutionalAspect, Cortes of Castile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: institutionalAspect Context triple: [History of the Crown of Castile, institutionalAspect, Cortes of Castile]
-
A.
institutionalLevel
Indicates the hierarchical or organizational tier at which an institution or its component operates or is classified.
-
B.
institutionalModel
Indicates the organizational or structural framework under which an institution is designed, governed, or operates.
-
C.
isInstitutional
Indicates that an entity functions as or is classified as an institution within the given context.
-
D.
institutionalPurpose
Indicates the intended function, mission, or role that an institution is designed or established to fulfill.
-
E.
inInstitution
Indicates that an entity is located within, belongs to, or is formally associated with a particular institution.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:33 p.m.