Triple
T29390171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SDHC |
E745350
|
entity |
| Predicate | supportsApplicationClass |
P32439
|
FINISHED |
| Object | A1 |
—
|
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: A1 | Statement: [SDHC, supportsApplicationClass, A1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsApplicationClass Context triple: [SDHC, supportsApplicationClass, A1]
-
A.
supportedClass
chosen
Indicates that one entity is a class or type that is recognized, handled, or operable within the capabilities or context provided by another entity.
-
B.
hasApplicationType
Indicates that an entity is associated with or classified by a specific type or category of application.
-
C.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
supportsImplementationOf
Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
-
E.
supportsClassification
Indicates that one entity provides the capability or functionality needed for another entity to perform or maintain a specific classification.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a03446ec72881909c5ff25a48baadb3 |
completed | May 12, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_6a03439b393c819084aa9b7ed0d5b6b0 |
completed | May 12, 2026, 3:13 p.m. |
Created at: April 28, 2026, 2:41 p.m.