Triple
T37678333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saafir |
E938153
|
entity |
| Predicate | battleHistory |
P133871
|
FINISHED |
| Object | noted for battle with Hieroglyphics on KMEL radio |
—
|
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: noted for battle with Hieroglyphics on KMEL radio | Statement: [Saafir, battleHistory, noted for battle with Hieroglyphics on KMEL radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleHistory Context triple: [Saafir, battleHistory, noted for battle with Hieroglyphics on KMEL radio]
-
A.
battlesWith
chosen
Indicates that two entities are engaged in active conflict, combat, or struggle against each other.
-
B.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
C.
battleDepicted
Indicates that a work or representation visually portrays a specific battle or combat event.
-
D.
combatRecord
Indicates that an entity maintains a documented history of its participation in combat or battles.
-
E.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:18 p.m.