Triple
T12181067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SoC |
E290220
|
entity |
| Predicate | integratesOn |
P103621
|
FINISHED |
| Object | single chip |
—
|
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: single chip | Statement: [SoC, integratesOn, single chip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratesOn Context triple: [SoC, integratesOn, single chip]
-
A.
integrates
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
B.
integralTo
Indicates that one entity is an essential, non-removable component or part of another entity, such that the whole depends on it to function or be complete.
-
C.
integratedOver
Indicates that a quantity or function has been mathematically integrated with respect to a specified variable or domain over a given interval or region.
-
D.
integralVersionUsedIn
Indicates that a specific integral version (e.g., of a component, document, or artifact) is utilized within or by another entity or process.
-
E.
integrandFeature
Indicates that a specific mathematical feature or property is part of, or characterizes, the integrand in an integration expression or operation.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91a83012c81908d04bbab5fdcd8c2 |
completed | April 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69d91510a258819090ef8fbdc2d8707b |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d91a7e0fc081909ec9769231e728a4 |
completed | April 10, 2026, 3:42 p.m. |
Created at: April 8, 2026, 9:50 p.m.