Triple
T29289530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ax Battler: A Legend of Golden Axe |
E742619
|
entity |
| Predicate | hasNPCs |
P111069
|
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: [Ax Battler: A Legend of Golden Axe, hasNPCs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNPCs Context triple: [Ax Battler: A Legend of Golden Axe, hasNPCs, yes]
-
A.
supportsNPCs
Indicates that an entity provides functionality or compatibility for non-player characters (NPCs) within a system or environment.
-
B.
hasHumanCharacters
Indicates that the subject includes or features characters that are human beings.
-
C.
hasCreature
Indicates that one entity possesses, contains, or is associated with a particular creature.
-
D.
hasCharacters
chosen
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
-
E.
hasFairyCharacters
Indicates that the subject includes or features characters that are fairies.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6653e73e081908ea14f73f88d5648 |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:01 p.m.