Triple
T30345318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALfheim Online |
E771853
|
entity |
| Predicate | usesHardwareInUniverse |
P87865
|
FINISHED |
| Object | AmuSphere |
—
|
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: AmuSphere | Statement: [ALfheim Online, usesHardwareInUniverse, AmuSphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHardwareInUniverse Context triple: [ALfheim Online, usesHardwareInUniverse, AmuSphere]
-
A.
hasHardware
Indicates that one entity possesses, includes, or is equipped with specific hardware components or devices.
-
B.
inUniverseTechnologyOf
chosen
Indicates that a technology exists within, and is part of, the fictional universe or setting associated with a given entity.
-
C.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
D.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
E.
hardwareUsedBy
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682073b00819087f197f3937071a5 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:55 p.m.