Triple
T1488001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Zaragoza |
E29511
|
entity |
| Predicate | effectOnSpain |
P28546
|
FINISHED |
| Object | recognized Portuguese rights to the Moluccas |
—
|
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: recognized Portuguese rights to the Moluccas | Statement: [Treaty of Zaragoza, effectOnSpain, recognized Portuguese rights to the Moluccas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnSpain Context triple: [Treaty of Zaragoza, effectOnSpain, recognized Portuguese rights to the Moluccas]
-
A.
effectOnDutchRepublic
Indicates the impact or consequences that something has on the Dutch Republic.
-
B.
strategicObjectiveSpain
Indicates that an entity has a strategic objective specifically related to Spain.
-
C.
hasSignificantSpanishInfluence
Indicates that one entity has been strongly shaped or notably affected by Spanish culture, language, practices, or presence.
-
D.
commanderForSpain
Indicates that a person serves or has served as a military commander on behalf of Spain.
-
E.
allyInWarOfTheSpanishSuccession
Indicates that the subject entity was an ally of the object entity during the War of the Spanish Succession.
- F. None of above. chosen
Provenance (4 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a44efc819084254614d8ea4669 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52c703c8190a56389b09d97659f |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8:12 p.m.