Triple
T4817411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Pamplona |
E107620
|
entity |
| Predicate | hasDefenders |
P54263
|
FINISHED |
| Object | Spanish garrison of Pamplona |
—
|
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: Spanish garrison of Pamplona | Statement: [Battle of Pamplona, hasDefenders, Spanish garrison of Pamplona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefenders Context triple: [Battle of Pamplona, hasDefenders, Spanish garrison of Pamplona]
-
A.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
-
B.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
C.
defenderIn
chosen
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
D.
defenceHandledBy
Indicates that responsibility for managing or conducting a defence is assigned to or carried out by a particular agent or entity.
-
E.
hasDefendants
Indicates that one or more entities serve as defendants in relation to a particular legal case or proceeding.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1dfa3481909d240d50ed0ee38c |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.