Triple
T33119391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BFG 9000 |
E847550
|
entity |
| Predicate | inUniversePowerSource |
P8164
|
FINISHED |
| Object | unknown advanced energy source |
—
|
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: unknown advanced energy source | Statement: [BFG 9000, inUniversePowerSource, unknown advanced energy source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniversePowerSource Context triple: [BFG 9000, inUniversePowerSource, unknown advanced energy source]
-
A.
hasPowerSource
chosen
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
B.
sourceOfPower
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
C.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
D.
poweringSystem
Indicates that one entity serves as the source of power or energy that enables the operation or functioning of another entity.
-
E.
inUniverseUse
Indicates that something is used or occurs within a particular fictional or conceptual universe, as opposed to in the real world or another setting.
- 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_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 1:27 a.m.