Triple
T2496427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guitar Hero |
E52160
|
entity |
| Predicate | hasMechanic |
P23573
|
FINISHED |
| Object | star power |
—
|
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: star power | Statement: [Guitar Hero, hasMechanic, star power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMechanic Context triple: [Guitar Hero, hasMechanic, star power]
-
A.
associatedWithMechanic
chosen
Indicates a relationship where an entity is connected or linked to a mechanic, such as a process, rule, or functional mechanism involved in its operation or behavior.
-
B.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
C.
mechanicalCompatibility
Indicates that two entities can function together properly from a mechanical standpoint, without interference, damage, or performance issues.
-
D.
isMechanicalOrElectronic
Indicates that something operates using mechanical components, electronic components, or a combination of both.
-
E.
backedByMechanism
Indicates that something is supported, enabled, or made possible by an underlying mechanism or system.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1abd3688190b5874249e1e333bc |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.