Triple
T37540546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flame Leviathan |
E933313
|
entity |
| Predicate | randomnessInvolved |
P83418
|
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: [Flame Leviathan, randomnessInvolved, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: randomnessInvolved Context triple: [Flame Leviathan, randomnessInvolved, true]
-
A.
introducesRandomnessIn
Indicates that something adds an element of unpredictability or variability into another process, system, or outcome.
-
B.
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.
-
C.
hardnessOfBeatingRandom
Indicates how difficult it is to defeat or outperform something when its behavior or outcome is determined randomly.
-
D.
canBeRandomized
Indicates that the entity is capable of having its state, order, or selection determined by a random process.
-
E.
randomizationRatio
Indicates the proportion in which subjects or items are randomly assigned to different groups or conditions.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.