Triple
T38641135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSMC N7P |
E938596
|
entity |
| Predicate | targetApplications |
P200018
|
FINISHED |
| Object | mobile SoCs |
—
|
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: mobile SoCs | Statement: [TSMC N7P, targetApplications, mobile SoCs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetApplications Context triple: [TSMC N7P, targetApplications, mobile SoCs]
-
A.
relatedApplication
Indicates that one application has a defined connection or association with another application, such as dependency, complementarity, or functional linkage.
-
B.
applicationTool
Indicates that one entity is a tool or instrument used to apply, operate, or carry out the function of another entity.
-
C.
surfaceApplication
Indicates that a substance, treatment, or process is applied to the outer surface of an object or material.
-
D.
applicationRange
Indicates the scope or extent within which something (such as a rule, function, or process) is validly applied or operates.
-
E.
hearsApplications
Indicates that an entity (such as a person or body) formally receives and considers applications submitted by others.
- F. None of above. chosen
Provenance (4 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69ff6a4c32dc819097f591944bee8851 |
completed | May 9, 2026, 5:09 p.m. |
Created at: May 3, 2026, 4:32 p.m.