Triple
T5752360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reddit Coins |
E126881
|
entity |
| Predicate | cannotBeUsedFor |
P30858
|
FINISHED |
| Object | purchasing physical goods |
—
|
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: purchasing physical goods | Statement: [Reddit Coins, cannotBeUsedFor, purchasing physical goods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeUsedFor Context triple: [Reddit Coins, cannotBeUsedFor, purchasing physical goods]
-
A.
cannotBeUsedWithout
Indicates that one entity is dependent on another such that it cannot function, operate, or be utilized unless the other entity is also present or in use.
-
B.
restrictedFromUseFor
chosen
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
-
C.
notTypicallyUsedFor
Indicates that something is generally not used for a particular purpose, function, or activity under normal circumstances.
-
D.
canBeUsedWithout
Indicates that one entity is capable of functioning or being utilized independently of another specified entity.
-
E.
canBeUsedOver
Indicates that one entity is suitable or valid for use in place of, or in relation to, another entity.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.