Triple
T26300047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Zamora |
E661529
|
entity |
| Predicate | recognizedRulerOf |
P141102
|
FINISHED |
| Object | Kingdom of Portugal |
—
|
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 Portugal | Statement: [Treaty of Zamora, recognizedRulerOf, Kingdom of Portugal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedRulerOf Context triple: [Treaty of Zamora, recognizedRulerOf, Kingdom of Portugal]
-
A.
recognizedAsRuler
chosen
Indicates that one entity is acknowledged or accepted by others as the legitimate ruler or sovereign authority.
-
B.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
C.
usedByRuler
Indicates that something is employed, utilized, or otherwise put to use by a ruler or governing authority.
-
D.
hasSignificantRuler
Indicates that an entity has or had a ruler whose leadership is considered historically or contextually important.
-
E.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
- 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_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 26, 2026, 10:15 p.m.