Triple
T32558712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War Boys |
E832160
|
entity |
| Predicate | battleCry |
P146223
|
FINISHED |
| Object | Witness me |
—
|
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: Witness me | Statement: [War Boys, battleCry, Witness me]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleCry Context triple: [War Boys, battleCry, Witness me]
-
A.
warCry
Indicates a relationship where an entity utters or performs a loud, rallying shout or chant intended to inspire allies or intimidate opponents, typically in a conflict or competitive context.
-
B.
battleCryAssociated
chosen
Indicates a relationship where a specific battle cry is linked or attributed to a particular entity, such as a person, group, or event.
-
C.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
-
D.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
E.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:03 a.m.