Triple
T26377996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altera Hardware Description Language |
E660949
|
entity |
| Predicate | notFullyStandardizedBy |
P58067
|
FINISHED |
| Object | IEEE |
—
|
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: IEEE | Statement: [Altera Hardware Description Language, notFullyStandardizedBy, IEEE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notFullyStandardizedBy Context triple: [Altera Hardware Description Language, notFullyStandardizedBy, IEEE]
-
A.
notStandardizedBy
Indicates that an entity has not been brought into conformity with a particular standard, method, or specification by the referenced agent or authority.
-
B.
isLessStandardizedThan
Indicates that one entity follows fewer or less rigid standards, norms, or formalized procedures than another entity.
-
C.
notFullyAdoptedIn
chosen
Indicates that something has not been completely or universally implemented, accepted, or put into practice within a specified context or domain.
-
D.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
E.
standardizedIn
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61071a4c4819090729e0c9789cf21 |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:02 p.m.