Triple
T29655247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warp Gate |
E750245
|
entity |
| Predicate | requiresPowerField |
P195351
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Warp Gate, requiresPowerField, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPowerField Context triple: [Warp Gate, requiresPowerField, true]
-
A.
requiresPortalOfPower
Indicates that performing this action or relationship is only possible through or by using a specific portal of power.
-
B.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
C.
supportedPower
Indicates that an entity is capable of providing, handling, or operating at a specified level or range of power.
-
D.
hasPowerFunction
Indicates that one entity serves as the power function or exponentiation operation applied to another entity.
-
E.
supportsPowerLevel
Indicates that one entity is capable of providing or sustaining the required power level for another entity or operation.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: April 28, 2026, 6:54 p.m.