Triple
T33119408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BFG 9000 |
E847550
|
entity |
| Predicate | playerCharacterUses |
P31799
|
FINISHED |
| Object | Doomguy |
—
|
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: Doomguy | Statement: [BFG 9000, playerCharacterUses, Doomguy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerCharacterUses Context triple: [BFG 9000, playerCharacterUses, Doomguy]
-
A.
usedByCharacter
chosen
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
-
B.
usesCharacter
Indicates that one entity employs, incorporates, or relies on a particular character (such as a symbol, letter, or persona) in its form, function, or representation.
-
C.
appliesToCharacter
Indicates that an action, rule, or property is specifically directed toward or relevant for a particular character.
-
D.
operatedByCharacter
Indicates that an operation, action, or process is carried out or controlled by a specific character.
-
E.
componentCharacter1
Indicates that one entity is the first (primary) character component or constituent part of another entity.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 1, 2026, 1:27 a.m.