Triple
T36557027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northfarthing |
E901723
|
entity |
| Predicate | battleInvolvedCharacter |
P76408
|
FINISHED |
| Object | Bandobras Took |
—
|
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: Bandobras Took | Statement: [Northfarthing, battleInvolvedCharacter, Bandobras Took]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleInvolvedCharacter Context triple: [Northfarthing, battleInvolvedCharacter, Bandobras Took]
-
A.
battleInvolvedIn
Indicates that an entity participated as a combatant or directly took part in a specific battle or military engagement.
-
B.
battleRelatedTo
Indicates a relationship where one entity is connected to, associated with, or relevant to a particular battle or combat event.
-
C.
battleParticipated
chosen
Indicates that an entity took part in a specific battle as a combatant or participant.
-
D.
battleInvolvedEmpire
Indicates that a particular empire participated as a combatant in the referenced battle.
-
E.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:11 p.m.