Triple
T9740792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HE-AAC v2 |
E236178
|
entity |
| Predicate | componentTechnology |
P38305
|
FINISHED |
| Object | AAC LC core |
—
|
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: AAC LC core | Statement: [HE-AAC v2, componentTechnology, AAC LC core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentTechnology Context triple: [HE-AAC v2, componentTechnology, AAC LC core]
-
A.
technologyNode
Indicates a relationship where an entity is associated with, implemented in, or characterized by a specific technology node or process technology level.
-
B.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
C.
technologyClass
Indicates the classification or category of technology to which an entity belongs.
-
D.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
-
E.
technologyBasis
chosen
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f29a5bc8190b2b391017405c71e |
completed | April 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.