Triple
T37511878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honor and Glory |
E932535
|
entity |
| Predicate | hasBattleScene |
P136051
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Honor and Glory, hasBattleScene, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattleScene Context triple: [Honor and Glory, hasBattleScene, yes]
-
A.
hasBattleScenes
chosen
Indicates that an entity (such as a work of fiction or media) contains scenes depicting battles or combat.
-
B.
hasFightSceneWith
Indicates that two entities participate together in a fight scene or combat sequence.
-
C.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
D.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
-
E.
hasTacticalBattles
Indicates that there are one or more specific tactical-level combat engagements occurring between the related entities.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 3, 2026, 4:17 p.m.