Triple
T33435995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VAPID |
E856239
|
entity |
| Predicate | tokenClaim |
P177027
|
FINISHED |
| Object | subject (sub) |
—
|
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: subject (sub) | Statement: [VAPID, tokenClaim, subject (sub)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tokenClaim Context triple: [VAPID, tokenClaim, subject (sub)]
-
A.
attributeClaim
Indicates that one entity asserts or specifies a particular attribute or property about another entity.
-
B.
tokenAudience
Indicates the intended group or recipients for whom a particular token (such as a digital asset, credential, or access right) is designed or targeted.
-
C.
recognizedClaimsOver
Indicates that one party has formally acknowledged or accepted the validity of certain claims made by another party.
-
D.
recognizedClaimOf
Indicates that one entity formally acknowledges the validity or legitimacy of a claim made by another entity.
-
E.
requiresClaim
Indicates that one entity can only be accessed, used, or fulfilled if a specific claim or entitlement has first been asserted or verified.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f814fcf48190ae4504154d1b2c05 |
completed | May 3, 2026, 7:24 a.m. |
Created at: May 1, 2026, 1:36 a.m.