Triple
T20350142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrono Trigger |
E495983
|
entity |
| Predicate | combatFeature |
P107524
|
FINISHED |
| Object | no random battles on world 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: no random battles on world map | Statement: [Chrono Trigger, combatFeature, no random battles on world map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatFeature Context triple: [Chrono Trigger, combatFeature, no random battles on world map]
-
A.
tacticalFeatureUsed
Indicates that a specific tactical feature, maneuver, or capability is employed or brought into play within a tactical situation or operation.
-
B.
battleCharacteristic
chosen
Indicates a relationship where a specific trait, quality, or feature is attributed to a battle or combat scenario.
-
C.
combatView
Indicates a perspective or representation of entities engaged in combat or battle-related interaction.
-
D.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
-
E.
warfareCapability
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6784eacf4819095504e541d1d284d |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.