Triple
T7417789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Horse |
E171171
|
entity |
| Predicate | certificationARIA |
P4915
|
FINISHED |
| Object | Multi-Platinum |
—
|
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: Multi-Platinum | Statement: [Dark Horse, certificationARIA, Multi-Platinum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: certificationARIA Context triple: [Dark Horse, certificationARIA, Multi-Platinum]
-
A.
hasARIAcertification
Indicates that an entity possesses an ARIA (Accessible Rich Internet Applications) certification attesting to compliance with relevant accessibility standards.
-
B.
certificationAustralia
chosen
Indicates that an entity holds or is associated with a certification that is valid or recognized in Australia.
-
C.
certificationBasis
Indicates the standard, criteria, or authority on which a certification or official approval is founded.
-
D.
typeOfCertification
Indicates the specific kind or category of certification associated with an entity.
-
E.
certificationLevel
Indicates the specific rank or degree of formal qualification or authorization that an entity has achieved within a defined certification system.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c9314c8190855b79a2e6ef3e9b |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.