Triple

T19505955
Position Surface form Disambiguated ID Type / Status
Subject Profibus PA E488020 entity
Predicate developedBy P73 FINISHED
Object PNO
PNO (PROFIBUS Nutzerorganisation) is the international user organization responsible for developing and promoting PROFIBUS and PROFINET industrial communication standards.
 E1379987 NE FINISHED

How this triple was built (4 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: PNO | Statement: [Profibus PA, developedBy, PNO]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: PNO
Context triple: [Profibus PA, developedBy, PNO]
  • A. PNO
    PNO is the station code for Panteones, a station on the Mexico City Metro system.
  • B. PNE
    PNE is a professional football club based in Preston, Lancashire, England, known for being one of the founding members of the English Football League.
  • C. PNE
    PNE is the National Rail station code for Penge East railway station in south London, England.
  • D. PNE
    PNE is the IATA airport code for Northeast Philadelphia Airport, a public airport serving the northeastern section of Philadelphia, Pennsylvania.
  • E. PNQ
    PNQ is the IATA airport code for Pune International Airport, a major civilian and military air hub serving the city of Pune in Maharashtra, India.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
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: PNO
Triple: [Profibus PA, developedBy, PNO]
Generated description
PNO (PROFIBUS Nutzerorganisation) is the international user organization responsible for developing and promoting PROFIBUS and PROFINET industrial communication standards.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: PNO
Target entity description: PNO (PROFIBUS Nutzerorganisation) is the international user organization responsible for developing and promoting PROFIBUS and PROFINET industrial communication standards.
  • A. PNO
    PNO is the station code for Panteones, a station on the Mexico City Metro system.
  • B. PNE
    PNE is a professional football club based in Preston, Lancashire, England, known for being one of the founding members of the English Football League.
  • C. PNE
    PNE is the National Rail station code for Penge East railway station in south London, England.
  • D. PNE
    PNE is the IATA airport code for Northeast Philadelphia Airport, a public airport serving the northeastern section of Philadelphia, Pennsylvania.
  • E. PNQ
    PNQ is the IATA airport code for Pune International Airport, a major civilian and military air hub serving the city of Pune in Maharashtra, India.
  • F. None of above. chosen

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_69d8e8d9d1c88190b01cd78b8be49384 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63511fc688190bd1474406060fa1b completed April 20, 2026, 2:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a07471f5348819087a442025b06f27d completed May 15, 2026, 4:17 p.m.
NEDg Description generation batch_6a07485e2e74819086ab5b5099079c81 completed May 15, 2026, 4:22 p.m.
NED2 Entity disambiguation (via description) batch_6a07498d29bc8190bb0eaf903dced2b0 completed May 15, 2026, 4:27 p.m.
Created at: April 10, 2026, 1:40 p.m.