Triple
T26637840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guerra de las Naranjas |
E668687
|
entity |
| Predicate | aliadoPrincipalDePortugal |
P161949
|
FINISHED |
| Object | Reino Unido |
—
|
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: Reino Unido | Statement: [Guerra de las Naranjas, aliadoPrincipalDePortugal, Reino Unido]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aliadoPrincipalDePortugal Context triple: [Guerra de las Naranjas, aliadoPrincipalDePortugal, Reino Unido]
-
A.
predecessorAsKingOfPortugal
Indicates that one entity served directly before another as the reigning king of Portugal.
-
B.
grantedToPortugal
Indicates that a right, privilege, territory, or other benefit has been formally conferred or assigned to Portugal.
-
C.
successorAsKingOfPortugal
Indicates that one entity becomes the next king of Portugal following another entity in the royal succession.
-
D.
monarchOnSpanishSide
Indicates that the monarch is aligned with, supports, or belongs to the Spanish side in a conflict, alliance, or political division.
-
E.
consequenceForPortugal
Indicates that one event, action, or situation results in a particular outcome or effect specifically for Portugal.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 2:28 a.m.