Triple
T7936704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HCL Technologies |
E184303
|
entity |
| Predicate | brand |
P1500
|
FINISHED |
| Object | HCLTech |
E184303
|
NE 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: HCLTech | Statement: [HCL Technologies, brand, HCLTech]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HCLTech Context triple: [HCL Technologies, brand, HCLTech]
-
A.
HCL Technologies
chosen
HCL Technologies is a global Indian IT services and consulting company known for providing software development, infrastructure management, and digital transformation solutions to enterprises worldwide.
-
B.
HCL
HCL is the commonly used abbreviation for HC Lugano, a professional ice hockey club based in Lugano, Switzerland.
-
C.
Infosys
Infosys is a leading Indian multinational IT services and consulting company known for its global technology solutions and innovation initiatives.
-
D.
EdgeVerve Systems
EdgeVerve Systems is a technology company specializing in software products and platforms, particularly in areas like banking, automation, and artificial intelligence.
-
E.
Capgemini
Capgemini is a global consulting, technology services, and digital transformation company headquartered in France.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aede3cc81908b0d3b54e68997b9 |
completed | March 31, 2026, 3:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc937366b8819091f08f8f7facf6f6 |
completed | April 1, 2026, 3:39 a.m. |
Created at: March 30, 2026, 5:08 p.m.