Triple
T26300040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Zamora |
E661529
|
entity |
| Predicate | recognizedSeparationFrom |
P165376
|
FINISHED |
| Object | Kingdom of León |
—
|
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: Kingdom of León | Statement: [Treaty of Zamora, recognizedSeparationFrom, Kingdom of León]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedSeparationFrom Context triple: [Treaty of Zamora, recognizedSeparationFrom, Kingdom of León]
-
A.
knownSeparation
chosen
Indicates that a separation or split between entities is recognized or has been established as a known fact.
-
B.
definedSeparationFrom
Indicates a formally specified distinction or boundary established between one entity and another.
-
C.
typeOfSeparation
Indicates the specific manner or category of separation that exists or occurred between entities.
-
D.
recognizedSeparateRuleOver
Indicates that one entity has formally acknowledged and applied a distinct, independent rule or principle in relation to another entity or context.
-
E.
recognizedSee
Indicates that one entity sees another and consciously recognizes or identifies what is being seen.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 26, 2026, 10:15 p.m.