Triple
T33119400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BFG 9000 |
E847550
|
entity |
| Predicate | playerPerception |
P183752
|
FINISHED |
| Object | ultimate weapon in Doom arsenal |
—
|
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: ultimate weapon in Doom arsenal | Statement: [BFG 9000, playerPerception, ultimate weapon in Doom arsenal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerPerception Context triple: [BFG 9000, playerPerception, ultimate weapon in Doom arsenal]
-
A.
publicPerception
Indicates how an individual, group, or entity is viewed, judged, or regarded by the general public or society at large.
-
B.
viewOnPerception
Indicates a relationship where one entity expresses or embodies a particular stance, interpretation, or opinion about the nature or process of perception.
-
C.
hasFanPerception
Indicates that an entity is perceived, interpreted, or regarded in a particular way by its fans or fan community.
-
D.
hasPerception
Indicates that one entity is aware of, senses, or recognizes another entity or phenomenon.
-
E.
typicalPerception
Indicates the usual or most common way an entity is perceived or experienced through the senses.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: May 1, 2026, 1:27 a.m.