Triple
T12048361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSMC N3B |
E286845
|
entity |
| Predicate | designUseCase |
P4831
|
FINISHED |
| Object | application processors |
—
|
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: application processors | Statement: [TSMC N3B, designUseCase, application processors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designUseCase Context triple: [TSMC N3B, designUseCase, application processors]
-
A.
designUse
chosen
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
B.
designMethod
Indicates that one entity is used as the method, approach, or technique by which another entity is designed or created.
-
C.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
D.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
-
E.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.