Triple
T19450731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breakout |
E486606
|
entity |
| Predicate | scoringMechanism |
P48244
|
FINISHED |
| Object | points awarded for breaking bricks |
—
|
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: points awarded for breaking bricks | Statement: [Breakout, scoringMechanism, points awarded for breaking bricks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoringMechanism Context triple: [Breakout, scoringMechanism, points awarded for breaking bricks]
-
A.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
B.
scoringType
chosen
Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
-
C.
scoringUnit
Indicates that one entity functions as a unit or component responsible for scoring or assigning scores to another entity.
-
D.
scoringRecord
Indicates that there exists a record documenting a scoring event or outcome associated with the given entities.
-
E.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338db7c081908793f23592ebef6b |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.