Triple
T7366697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mega Mushroom |
E169886
|
entity |
| Predicate | scoreEffect |
P77094
|
FINISHED |
| Object | may grant points for each object destroyed |
—
|
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: may grant points for each object destroyed | Statement: [Mega Mushroom, scoreEffect, may grant points for each object destroyed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreEffect Context triple: [Mega Mushroom, scoreEffect, may grant points for each object destroyed]
-
A.
scoreUsedFor
Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
-
B.
scoreScale
Indicates the scale or range on which a score or rating is expressed or measured.
-
C.
scoreAfterPlay
Indicates the numerical score that results immediately after a specific play or action has been completed.
-
D.
scoresWhen
Indicates that one entity achieves a score or points at the time or under the condition specified by another entity or event.
-
E.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
- 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f26c050c8190a2d009b45d920490 |
completed | March 27, 2026, 9:11 p.m. |
Created at: March 27, 2026, 3:06 p.m.