Triple
T9782933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verilog |
E237419
|
entity |
| Predicate | designAbstractionLevel |
P17210
|
FINISHED |
| Object | behavioral |
—
|
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: behavioral | Statement: [Verilog, designAbstractionLevel, behavioral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designAbstractionLevel Context triple: [Verilog, designAbstractionLevel, behavioral]
-
A.
representationLevel
chosen
Indicates the degree or layer at which something stands in for, models, or symbolizes something else (e.g., more concrete vs. more abstract representation).
-
B.
automationLevel
Indicates the degree to which a process, task, or system is performed automatically rather than manually.
-
C.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
-
D.
developmentScale
Indicates the relative size, intensity, or extent to which something is developed or has progressed in its development.
-
E.
configurationLevel
Indicates the degree or tier of settings or parameters applied to configure something within a system or context.
- 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1b5714481908bf74b8bf3e4e6e8 |
completed | April 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:27 p.m.