Triple
T35630912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trastámara county |
E1029581
|
entity |
| Predicate | politicalHierarchy |
P196900
|
FINISHED |
| Object | below kingdom level |
—
|
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: below kingdom level | Statement: [Trastámara county, politicalHierarchy, below kingdom level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalHierarchy Context triple: [Trastámara county, politicalHierarchy, below kingdom level]
-
A.
socialHierarchy
Indicates a relationship where entities are ordered or ranked by social status, power, or authority relative to one another.
-
B.
constitutionalHierarchy
Indicates that one entity holds a superior or subordinate status to another within a formal constitutional or foundational legal framework.
-
C.
partyHierarchyRank
Indicates the relative position or level of an entity within an ordered party hierarchy.
-
D.
powerStructure
Indicates how authority, control, and decision-making are distributed and organized among entities within a system or group.
-
E.
partOfTerritorialHierarchy
chosen
Indicates that one territorial unit is contained within or subordinate to another within an administrative or geographic hierarchy.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:05 p.m.