Triple
T37458778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piloted Sky Golem |
E930864
|
entity |
| Predicate | hasRandomEffect |
P83418
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Piloted Sky Golem, hasRandomEffect, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRandomEffect Context triple: [Piloted Sky Golem, hasRandomEffect, yes]
-
A.
isRandomized
chosen
Indicates that the selection, ordering, or assignment associated with something is determined by a random process rather than a fixed or predetermined rule.
-
B.
spatialEffect
Indicates a spatial relationship where one entity affects or alters the position, arrangement, or spatial properties of another.
-
C.
canBeRandomized
Indicates that the entity is capable of having its state, order, or selection determined by a random process.
-
D.
hasInteractionEffects
Indicates that one entity’s presence, action, or state alters, influences, or modifies the behavior, effect, or outcome associated with another entity.
-
E.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 3, 2026, 4:17 p.m.