Triple
T24445482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KLA Corporation |
E616389
|
entity |
| Predicate | hasR&DCenter |
P47071
|
FINISHED |
| Object | Israel |
—
|
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: Israel | Statement: [KLA Corporation, hasR&DCenter, Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasR&DCenter Context triple: [KLA Corporation, hasR&DCenter, Israel]
-
A.
hasRAndDCenterIn
chosen
Indicates that an entity maintains a research and development (R&D) center located in a specified place.
-
B.
hasServiceCenter
Indicates that an entity maintains or is associated with a service center that provides support, repair, or maintenance services.
-
C.
hasCircuitCentre
Indicates that an entity has, is associated with, or is organized around a specific circuit center that serves as its focal or central point.
-
D.
hasMajorServiceCenter
Indicates that an entity hosts or contains a primary or significant service facility that supports operations or customers.
-
E.
hasDispatchCenter
Indicates that an entity is served, managed, or coordinated by a specific dispatch center.
- 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29852c6908190ab5186cee3693625 |
completed | April 29, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:17 a.m.