Triple
T25932397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zen |
E653467
|
entity |
| Predicate | processNodeSupplier |
P154337
|
FINISHED |
| Object | GlobalFoundries |
—
|
NE NERFINISHED |
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: GlobalFoundries | Statement: [Zen, processNodeSupplier, GlobalFoundries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processNodeSupplier Context triple: [Zen, processNodeSupplier, GlobalFoundries]
-
A.
processNode
Indicates performing an operation or series of operations on a node within a data structure or system.
-
B.
intendedProcessNode
Indicates that one entity is designated or planned to serve as the process node for another entity within a process or workflow.
-
C.
firstStageSupplier
chosen
Indicates that one entity serves as a direct, primary supplier to another in the first stage of a supply chain or procurement relationship.
-
D.
processNodeVendor
Indicates that a node is being handled or operated on by a specific vendor or vendor-related process.
-
E.
primaryProcessNodeRange
Indicates the span or range of primary process nodes associated with or covered by a given element 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60419ef7881909fe061a3d1aa1ddf |
completed | May 2, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 8:37 a.m.