Triple
T5665064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leader of the Opposition (Spain) |
E124838
|
entity |
| Predicate | isCustomaryPosition |
P21161
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Leader of the Opposition (Spain), isCustomaryPosition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCustomaryPosition Context triple: [Leader of the Opposition (Spain), isCustomaryPosition, yes]
-
A.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
-
B.
initiallyPositionedAs
Indicates that one entity’s starting or original position is specified relative to another entity or reference frame.
-
C.
hasCanonicalPosition
chosen
Indicates that an entity occupies a standard, officially recognized, or authoritative position or location within a defined structure or system.
-
D.
isCeremoniallyDistinctFrom
Indicates that two entities are formally separated or differentiated from each other within a ritual, ceremonial, or symbolic context.
-
E.
isAt
Indicates that one entity is located at or present in the place or position of 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.