Triple
T30273911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twisted |
E769878
|
entity |
| Predicate | certificationUSAuthority |
P87322
|
FINISHED |
| Object | RIAA |
—
|
NE NERFINISHED |
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: RIAA | Statement: [Twisted, certificationUSAuthority, RIAA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: certificationUSAuthority Context triple: [Twisted, certificationUSAuthority, RIAA]
-
A.
certificationUS
Indicates that an entity holds or is associated with a certification that is recognized, issued, or valid within the United States.
-
B.
canCertify
chosen
Indicates that one entity has the authority or capability to officially certify another entity or its attributes.
-
C.
certificationBy
Indicates that one entity formally attests to, approves, or validates the qualifications, standards, or authenticity of another entity.
-
D.
legalStatusOfAuthority
Indicates the legal status or standing that a particular authority holds within a given legal or regulatory framework.
-
E.
isCertified
Indicates that an entity has been officially recognized as meeting specific standards or qualifications by an authorized body.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680d66a008190b41625688670e25b |
completed | May 2, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:44 p.m.