Triple
T26377979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altera Hardware Description Language |
E660949
|
entity |
| Predicate | supportedByTool |
P9867
|
FINISHED |
| Object | Altera MAX+PLUS II |
—
|
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: Altera MAX+PLUS II | Statement: [Altera Hardware Description Language, supportedByTool, Altera MAX+PLUS II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedByTool Context triple: [Altera Hardware Description Language, supportedByTool, Altera MAX+PLUS II]
-
A.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
B.
isSupportedBy
chosen
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
C.
supportsBackupTool
Indicates that one entity provides compatibility with or functionality for a specified backup tool.
-
D.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
E.
usedByTool
Indicates that a particular tool is employed or operated by a specified agent or 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 26, 2026, 11:02 p.m.