Triple
T29372018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blazing Lazers |
E744878
|
entity |
| Predicate | developerReputation |
P179931
|
FINISHED |
| Object | known for shoot-'em-up games |
—
|
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: known for shoot-'em-up games | Statement: [Blazing Lazers, developerReputation, known for shoot-'em-up games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerReputation Context triple: [Blazing Lazers, developerReputation, known for shoot-'em-up games]
-
A.
programmingReputation
Indicates the level of recognition or esteem an entity has earned for its programming-related skills, contributions, or performance.
-
B.
engineeringReputation
Indicates the perceived quality, credibility, or esteem of an entity’s engineering capabilities or output as judged by others.
-
C.
designReputation
Indicates the perceived quality or standing of an entity based on others’ judgments of its design.
-
D.
scoringReputation
Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
-
E.
performanceReputation
Indicates the perceived quality or reliability of an entity’s past or expected performance as judged by others.
- F. None of above. chosen
Provenance (4 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: April 28, 2026, 2:28 p.m.