Triple
T33359227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Battle of Brega (2011) |
E854164
|
entity |
| Predicate | statusOfBregaAfterBattle |
P109227
|
FINISHED |
| Object | remained under rebel control |
—
|
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: remained under rebel control | Statement: [First Battle of Brega (2011), statusOfBregaAfterBattle, remained under rebel control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfBregaAfterBattle Context triple: [First Battle of Brega (2011), statusOfBregaAfterBattle, remained under rebel control]
-
A.
statusAfterBattle
chosen
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
B.
statusDuringBattle
Indicates the condition or state an entity has while a specific battle or combat event is taking place.
-
C.
statusAfterAttack
Indicates the resulting condition or state of an entity after an attack has occurred.
-
D.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
E.
statusAfterBattleForAzeroth
Indicates the condition or state of an entity following the events of the Battle for Azeroth.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: May 1, 2026, 1:34 a.m.