Triple
T2225466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMIC |
E48637
|
entity |
| Predicate | designRequires |
P1840
|
FINISHED |
| Object | electromagnetic simulation |
—
|
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: electromagnetic simulation | Statement: [MMIC, designRequires, electromagnetic simulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designRequires Context triple: [MMIC, designRequires, electromagnetic simulation]
-
A.
requiredDesignElement
chosen
Indicates that one entity must include, use, or incorporate another entity as a necessary design component or feature.
-
B.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
C.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
D.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
E.
designSpecifiedBy
Indicates that the design or specification of one entity is defined, authored, or determined 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc03ffcbc8190a27e32af831c7be5 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.