Triple
T1488002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Zaragoza |
E29511
|
entity |
| Predicate | effectOnPortugal |
P8692
|
FINISHED |
| Object | confirmed Portuguese control over 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: confirmed Portuguese control over the Moluccas | Statement: [Treaty of Zaragoza, effectOnPortugal, confirmed Portuguese control over the Moluccas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnPortugal Context triple: [Treaty of Zaragoza, effectOnPortugal, confirmed Portuguese control over the Moluccas]
-
A.
effectOnDutchRepublic
Indicates the impact or consequences that something has on the Dutch Republic.
-
B.
limitedPortugalTo
Indicates that something is restricted in scope, effect, or applicability specifically to Portugal.
-
C.
affectedCountry
chosen
Indicates that a particular country is impacted or influenced by an event, action, or condition.
-
D.
strategicObjectiveSpain
Indicates that an entity has a strategic objective specifically related to Spain.
-
E.
hasHistoricalInfluenceFrom
Indicates that one entity’s characteristics, development, or significance have been shaped or affected by the past actions, ideas, or legacy 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_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. |
Created at: March 1, 2026, 8:12 p.m.