Triple
T36833748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | siege of Santarém |
E910213
|
entity |
| Predicate | militaryGoalOfPortuguese |
P192885
|
FINISHED |
| Object | maintain sovereignty over Santarém |
—
|
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: maintain sovereignty over Santarém | Statement: [siege of Santarém, militaryGoalOfPortuguese, maintain sovereignty over Santarém]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryGoalOfPortuguese Context triple: [siege of Santarém, militaryGoalOfPortuguese, maintain sovereignty over Santarém]
-
A.
grantedToPortugal
Indicates that a right, privilege, territory, or other benefit has been formally conferred or assigned to Portugal.
-
B.
tacticsUsedByPortugal
Indicates that certain tactics are employed or utilized by Portugal.
-
C.
aliadoPrincipalDePortugal
Indicates that one entity serves as the primary ally of Portugal in a political, military, or strategic context.
-
D.
consequenceForPortugal
Indicates that one event, action, or situation results in a particular outcome or effect specifically for Portugal.
-
E.
returnedToPortugal
Indicates that an entity went back to Portugal after having been away.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
| PDg | Predicate description generation | batch_69fd2cf29f808190856ab1d43a51d5c7 |
completed | May 8, 2026, 12:23 a.m. |
Created at: May 3, 2026, 4:13 p.m.