Triple
T26021092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twitch Bits |
E647153
|
entity |
| Predicate | isPlatformLocked |
P93397
|
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: [Twitch Bits, isPlatformLocked, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlatformLocked Context triple: [Twitch Bits, isPlatformLocked, true]
-
A.
isKeyPlatformFor
Indicates that one entity serves as a primary or foundational platform that enables, supports, or underpins the activities, services, or operations of another entity.
-
B.
canBeLocked
chosen
Indicates that an entity has the capability to be secured or made inaccessible by applying a lock or locking mechanism.
-
C.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
D.
hasLock
Indicates that one entity possesses or is secured by a lock associated with another entity.
-
E.
usesLockSystem
Indicates that one entity employs or relies on a locking mechanism or lock-based system provided by 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605e5af4081909e3862d44e313d7f |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 9:03 a.m.