Triple
T26614317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of The Hague (1703) |
E668015
|
entity |
| Predicate | aligned |
P6442
|
FINISHED |
| Object | 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: Portugal | Statement: [Treaty of The Hague (1703), aligned, Portugal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aligned Context triple: [Treaty of The Hague (1703), aligned, Portugal]
-
A.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
-
B.
alignedOrganization
Indicates that one organization is ideologically, strategically, or operationally in agreement or coordination with another organization.
-
C.
alignmentGoal
Indicates that an entity has a desired or target alignment state it aims to achieve or maintain.
-
D.
alignmentLeader
Indicates that one entity serves as the primary leader or guiding figure responsible for directing or coordinating the alignment of others.
-
E.
alignsWith
chosen
Indicates that one entity is in agreement, harmony, or consistent correspondence with another in terms of position, direction, standard, or principle.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f615ab004c8190940650384f1e161c |
completed | May 2, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:18 a.m.