Triple
T4814848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barak |
E107162
|
entity |
| Predicate | conditionForBattle |
P59798
|
FINISHED |
| Object | insisted Deborah accompany him |
—
|
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: insisted Deborah accompany him | Statement: [Barak, conditionForBattle, insisted Deborah accompany him]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionForBattle Context triple: [Barak, conditionForBattle, insisted Deborah accompany him]
-
A.
allyInBattle
Indicates that two or more entities cooperate on the same side as partners during a specific battle or combat situation.
-
B.
controlDuringBattle
Indicates that one entity exerts command, influence, or strategic direction over another specifically in the context of a battle or combat situation.
-
C.
battleSystem
Indicates a relationship where entities are engaged in or governed by a structured combat or conflict-resolution mechanism.
-
D.
mainBattle
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or entity.
-
E.
functionDuringBattle
Indicates a functional role, effect, or behavior that specifically occurs or is active during a battle.
- 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_69bd43f779448190b92885cb70abb6c2 |
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. |
| PDg | Predicate description generation | batch_69bd6dda5e808190a26ec85e4499d8e4 |
completed | March 20, 2026, 3:55 p.m. |
Created at: March 20, 2026, 1:23 p.m.