Triple
T37458025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Totemic Call |
E930847
|
entity |
| Predicate | effectTarget |
P53074
|
FINISHED |
| Object | Battlefield |
—
|
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: Battlefield | Statement: [Totemic Call, effectTarget, Battlefield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectTarget Context triple: [Totemic Call, effectTarget, Battlefield]
-
A.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
B.
ultimateEffect
Indicates the final or overall outcome that results from a preceding action, condition, or sequence of events.
-
C.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
D.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
E.
capturesEffectOf
Indicates that one entity represents or records the impact, consequence, or outcome produced by another entity or process.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:17 p.m.