Triple

T28509041
Position Surface form Disambiguated ID Type / Status
Subject Asterisk E721433 entity
Predicate supportsScripting P203 FINISHED
Object AGI (Asterisk Gateway Interface)
AGI (Asterisk Gateway Interface) is a scripting interface for the Asterisk telephony platform that allows external programs to control and interact with phone calls in real time.
E1821856 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: AGI (Asterisk Gateway Interface) | Statement: [Asterisk, supportsScripting, AGI (Asterisk Gateway Interface)]
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: AGI (Asterisk Gateway Interface)
Triple: [Asterisk, supportsScripting, AGI (Asterisk Gateway Interface)]
Generated description
AGI (Asterisk Gateway Interface) is a scripting interface for the Asterisk telephony platform that allows external programs to control and interact with phone calls in real time.

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_69f01a5c072081908c7b04bcf6478da9 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f64f7388a88190a80dc4730f92eded completed May 2, 2026, 7:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1cac501098819084232ac999d17407 completed May 31, 2026, 9:46 p.m.
NEDg Description generation batch_6a1cacfc26bc8190ad65e3f8ef7d6d7b completed May 31, 2026, 9:49 p.m.
NED2 Entity disambiguation (via description) batch_6a1cadf50e1c81908235678a32385afb completed May 31, 2026, 9:53 p.m.
Created at: April 28, 2026, 3:11 a.m.