Triple
T2342665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaties of Córdoba |
E45059
|
entity |
| Predicate | legalStatusInSpain |
P2250
|
FINISHED |
| Object | not ratified |
—
|
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: not ratified | Statement: [Treaties of Córdoba, legalStatusInSpain, not ratified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInSpain Context triple: [Treaties of Córdoba, legalStatusInSpain, not ratified]
-
A.
certificationSpain
Indicates that an entity holds or is associated with a certification that is valid, issued, or recognized in Spain.
-
B.
legalStatusInEuropeanUnion
Indicates the legal status or standing that an entity holds within the jurisdictional framework of the European Union.
-
C.
legalStatusInManyCountries
Indicates that the subject has a particular legal classification or standing that is recognized across numerous countries.
-
D.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
E.
hasLegalStatus
chosen
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.