Triple
T38644994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devourer |
E938691
|
entity |
| Predicate | hasSplashEffect |
P199282
|
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: [Devourer, hasSplashEffect, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSplashEffect Context triple: [Devourer, hasSplashEffect, true]
-
A.
hasSplashdown
Indicates that an object or vehicle returns from flight or space and lands in water rather than on solid ground.
-
B.
hasSpinEffect
Indicates that one entity causes or exhibits a spinning or rotational effect on another entity.
-
C.
hasOnboardEffects
Indicates that something produces effects or consequences specifically on board a vehicle, vessel, or similar platform.
-
D.
hasIntroEffect
Indicates that an entity produces a specific effect or outcome when it is first introduced, activated, or brought into play.
-
E.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
| PDg | Predicate description generation | batch_69ff29d77f48819085304ed5e92eb906 |
completed | May 9, 2026, 12:34 p.m. |
Created at: May 3, 2026, 4:32 p.m.