Triple
T20182742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roshambo |
E492772
|
entity |
| Predicate | hasOutcomeRule |
P133032
|
FINISHED |
| Object | rock beats scissors |
—
|
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: rock beats scissors | Statement: [Roshambo, hasOutcomeRule, rock beats scissors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutcomeRule Context triple: [Roshambo, hasOutcomeRule, rock beats scissors]
-
A.
hasOutcomeIndicator
Indicates that something is associated with a specific measure or indicator used to evaluate its outcome or results.
-
B.
hasEventOutcome
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
-
C.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
D.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
E.
hasRuleFor
chosen
Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668ef9370819091a8479f811002a9 |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.