Triple
T37458026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Totemic Call |
E930847
|
entity |
| Predicate | effectRandomness |
P149868
|
FINISHED |
| Object | Random Totem |
—
|
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: Random Totem | Statement: [Totemic Call, effectRandomness, Random Totem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectRandomness Context triple: [Totemic Call, effectRandomness, Random Totem]
-
A.
introducesRandomnessIn
chosen
Indicates that something adds an element of unpredictability or variability into another process, system, or outcome.
-
B.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
C.
effectOnUsage
Indicates how one factor or condition changes the way something is used, including the extent, manner, or frequency of its usage.
-
D.
isRandomized
Indicates that the selection, ordering, or assignment associated with something is determined by a random process rather than a fixed or predetermined rule.
-
E.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
- 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_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 3, 2026, 4:17 p.m.