Triple
T13812641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro D2 |
E331930
|
entity |
| Predicate | usesBonusPointSystem |
P64949
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pro D2, usesBonusPointSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBonusPointSystem Context triple: [Pro D2, usesBonusPointSystem, true]
-
A.
usesPointsSystem
chosen
Indicates that an entity operates or functions based on a structured points-based system for evaluation, rewards, or progression.
-
B.
supportsBonus
Indicates that one entity provides or enables an additional benefit, reward, or bonus for another entity.
-
C.
rewardUse
Indicates that one entity grants or provides a reward in response to the use or utilization of another entity.
-
D.
usesIncentive
Indicates that one entity employs or applies an incentive (such as a reward, benefit, or motivation) to influence the behavior or decisions of another entity.
-
E.
hasBadgeSystem
Indicates that an entity includes or supports a badge-based system for recognizing or tracking achievements, statuses, or milestones.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de027198f8819095da3e714ac241f5 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.