Triple
T12399916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count-Duke |
E296222
|
entity |
| Predicate | governmentalSphere |
P18467
|
FINISHED |
| Object | Spanish court politics |
—
|
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: Spanish court politics | Statement: [Count-Duke, governmentalSphere, Spanish court politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentalSphere Context triple: [Count-Duke, governmentalSphere, Spanish court politics]
-
A.
politicalSphere
chosen
Indicates involvement or relevance within the domain of politics, governance, or public policy activities and interactions.
-
B.
governmentalCore
Indicates that something serves as a central, essential, or foundational part of a government or governmental system.
-
C.
governmentalFunction
Indicates that an entity performs, embodies, or is responsible for an official role, duty, or activity of a government.
-
D.
countryGovernment
Indicates the type or form of government that exercises authority over a given country.
-
E.
governmentInvolvement
Indicates that a government participates in, influences, regulates, or otherwise plays a role in the specified activity, process, or 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9401cbfd481908ee6e765da3d12cb |
completed | April 10, 2026, 6:23 p.m. |
| PD | Predicate disambiguation | batch_69d93ed4cea08190ad374d3f6a798053 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:55 p.m.