Triple
T8412711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shining Force |
E198660
|
entity |
| Predicate | combatPerspective |
P59540
|
FINISHED |
| Object | top-down tactical map |
—
|
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: top-down tactical map | Statement: [Shining Force, combatPerspective, top-down tactical map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatPerspective Context triple: [Shining Force, combatPerspective, top-down tactical map]
-
A.
militaryTacticsFaced
Indicates that an entity encountered or had to contend with specific military tactics employed by another entity.
-
B.
viewOnWar
Indicates a stance, opinion, or perspective that an entity holds regarding war or armed conflict.
-
C.
combatRelated
Indicates that the entities are connected through participation in, involvement with, or direct association to combat or military conflict.
-
D.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
-
E.
militaryConflictView
chosen
Indicates a perspective, interpretation, or representation of a specific military conflict or battle.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e18e7c8190a30b14136dee3d93 |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.