Triple
T7895412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3D Pinball for Windows – Space Cadet |
E183331
|
entity |
| Predicate | hasScoreSystem |
P79635
|
FINISHED |
| Object | points-based scoring |
—
|
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-based scoring | Statement: [3D Pinball for Windows – Space Cadet, hasScoreSystem, points-based scoring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScoreSystem Context triple: [3D Pinball for Windows – Space Cadet, hasScoreSystem, points-based scoring]
-
A.
hasGradeSystem
Indicates that one entity uses, follows, or is governed by a particular grading or evaluation system defined by another entity.
-
B.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
C.
hasScoreboard
Indicates that one entity is equipped with or associated with a scoreboard used to display scores or results.
-
D.
hasBadgeSystem
Indicates that an entity includes or supports a badge-based system for recognizing or tracking achievements, statuses, or milestones.
-
E.
introducedScoringSystem
Indicates that an entity initiated or brought into use a particular scoring system.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a174574819084270dbb6fcbb7fe |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 5:01 p.m.