Triple
T36523453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 7185 |
E900235
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object |
Extended Pascal
Extended Pascal is an enhanced version of the Pascal programming language that adds standardized features such as modularity, separate compilation, and improved data types beyond those defined in ISO 7185.
|
E2187149
|
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: Extended Pascal | Statement: [ISO 7185, relatedTo, Extended Pascal]
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: Extended Pascal Triple: [ISO 7185, relatedTo, Extended Pascal]
Generated description
Extended Pascal is an enhanced version of the Pascal programming language that adds standardized features such as modularity, separate compilation, and improved data types beyond those defined in ISO 7185.
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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c215b8b8819088b38537619fc465 |
completed | May 3, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbe1cc7c81909ad71f59aa5042b0 |
completed | June 23, 2026, 1:05 a.m. |
| NEDg | Description generation | batch_6a39dc86e8cc8190b6be021ce03abfbf |
completed | June 23, 2026, 1:08 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a39de5091f8819082f7dd6f5dfff703 |
completed | June 23, 2026, 1:16 a.m. |
Created at: May 3, 2026, 4:11 p.m.