Triple
T26637817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guerra de las Naranjas |
E668687
|
entity |
| Predicate | oponenteDe |
P86168
|
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: [Guerra de las Naranjas, oponenteDe, Portugal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oponenteDe Context triple: [Guerra de las Naranjas, oponenteDe, Portugal]
-
A.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
B.
laterOpponent
Indicates that one entity becomes the opponent of another at a later time or stage, following an earlier phase or matchup.
-
C.
wasOpponentOf
chosen
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
-
D.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
E.
opponentInScenario
Indicates that one entity is an adversary or rival of another within a specific scenario, context, or situation.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6162d48f88190b43087b02cbf30e8 |
completed | May 2, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:28 a.m.