Triple
T37459333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptulon |
E930878
|
entity |
| Predicate | hasBattlecry |
P195330
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Neptulon, hasBattlecry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattlecry Context triple: [Neptulon, hasBattlecry, true]
-
A.
hasHeroPower
Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to another entity.
-
B.
battlecry
Indicates a relationship where an entity utters or uses a shouted phrase or chant to inspire, rally, or signal others, typically in preparation for or during conflict.
-
C.
battlecryChoice
Indicates the specific battle cry that an entity selects or uses, typically as a vocal expression before or during combat.
-
D.
battlecryText
Indicates the characteristic phrase or shout used as a battle cry during a conflict or confrontation.
-
E.
summonedMinionKeyword
Indicates that one entity has been brought into play or created as a subordinate or controlled minion by another entity.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
| PDg | Predicate description generation | batch_69fdbaa1313081908beea28a5597ae40 |
completed | May 8, 2026, 10:27 a.m. |
Created at: May 3, 2026, 4:17 p.m.