Triple
T2869333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of The Hague (1720) |
E63519
|
entity |
| Predicate | limitedAmbitionsOf |
P28788
|
FINISHED |
| Object | Spain in Italy |
—
|
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: Spain in Italy | Statement: [Treaty of The Hague (1720), limitedAmbitionsOf, Spain in Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedAmbitionsOf Context triple: [Treaty of The Hague (1720), limitedAmbitionsOf, Spain in Italy]
-
A.
aimedToLimit
chosen
Indicates an action or policy that was intentionally directed toward restricting, reducing, or constraining something.
-
B.
territorialAmbition
Indicates a desire or intent by one entity to expand its control, ownership, or influence over additional geographic areas or territories.
-
C.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
D.
legacyGoal
Indicates that an entity has a long-term, enduring objective or impact it aims to leave behind beyond its immediate actions or existence.
-
E.
missionScope
Indicates the defined range, objectives, and boundaries within which a mission or operation is intended to be carried out.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfe15ff081908dd1dad62c292b2b |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.