Triple
T37990847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crisis Core: Final Fantasy VII |
E947818
|
entity |
| Predicate | battleSystemFeature |
P169307
|
FINISHED |
| Object | Digital Mind Wave |
—
|
NE NERFINISHED |
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: Digital Mind Wave | Statement: [Crisis Core: Final Fantasy VII, battleSystemFeature, Digital Mind Wave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleSystemFeature Context triple: [Crisis Core: Final Fantasy VII, battleSystemFeature, Digital Mind Wave]
-
A.
battleSystem
Indicates a relationship where entities are engaged in or governed by a structured combat or conflict-resolution mechanism.
-
B.
combatSystemFeature
chosen
Indicates that one entity is a feature, mechanic, or component belonging to or used within another entity’s combat system.
-
C.
featuresBattle
Indicates that one entity includes, presents, or involves a battle as a significant element or event.
-
D.
battleCharacteristic
Indicates a relationship where a specific trait, quality, or feature is attributed to a battle or combat scenario.
-
E.
battlecryChoice
Indicates the specific battle cry that an entity selects or uses, typically as a vocal expression before or during combat.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:20 p.m.