Triple

T35236455
Position Surface form Disambiguated ID Type / Status
Subject Board of Directors of Infosys E1017390 entity
Predicate follows P134 FINISHED
Object Infosys Code of Conduct
Infosys Code of Conduct is the company’s formal ethical framework that sets out the principles, values, and standards of behavior expected from its leadership and employees in conducting business.
E64550 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: Infosys Code of Conduct | Statement: [Board of Directors of Infosys, follows, Infosys Code of Conduct]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Infosys Code of Conduct
Triple: [Board of Directors of Infosys, follows, Infosys Code of Conduct]
Generated description
Infosys Code of Conduct is the company’s formal ethical framework that sets out the principles, values, and standards of behavior expected from its leadership and employees in conducting business.

Provenance (5 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_69f76de12e4c8190bc46b71a32858356 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78eeed46c8190b7de000660a5fc49 completed May 3, 2026, 6:07 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38041fe36c819084cfdfe59aac93e7 completed June 21, 2026, 3:32 p.m.
NEDg Description generation batch_6a3804add67c819096139f4115a709d6 completed June 21, 2026, 3:35 p.m.
NED2 Entity disambiguation (via description) batch_6a380636124881908b4a1894357525a9 completed June 21, 2026, 3:41 p.m.
Created at: May 3, 2026, 4:02 p.m.