Triple
T32139420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASIC |
E820861
|
entity |
| Predicate | hasDesignFlow |
P1529
|
FINISHED |
| Object | specification |
—
|
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: specification | Statement: [ASIC, hasDesignFlow, specification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignFlow Context triple: [ASIC, hasDesignFlow, specification]
-
A.
hasDesign
chosen
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
hasDesignPhase
Indicates that an entity is associated with or undergoes a specific design phase within a broader process or lifecycle.
-
C.
hasDesignIntent
Indicates that one entity embodies or reflects the planned purpose, function, or conceptual intent defined by another entity.
-
D.
hasDesignInputFrom
Indicates that the design of one entity is based on, influenced by, or derived from input provided by another entity.
-
E.
hasDesignMovement
Indicates that something is associated with, characterized by, or created within a particular design movement or stylistic school.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 1, 2026, 12:30 a.m.