Triple
T4442550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eiffel |
E96205
|
entity |
| Predicate | standardName |
P66
|
FINISHED |
| Object |
ISO/IEC 25436
ISO/IEC 25436 is the international standard that formally defines the Eiffel programming language.
|
E440616
|
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: ISO/IEC 25436 | Statement: [Eiffel, standardName, ISO/IEC 25436]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO/IEC 25436 Context triple: [Eiffel, standardName, ISO/IEC 25436]
-
A.
ISO/IEC 23273
ISO/IEC 23273 is an international standard that specifies safety requirements for hydrogen-fueled road vehicles, particularly focusing on fuel cell vehicle safety.
-
B.
ISO/IEC 23271
ISO/IEC 23271 is the international standard that defines the Common Language Infrastructure (CLI), the core runtime and execution environment underlying technologies like Microsoft .NET.
-
C.
ISO/IEC 24748
ISO/IEC 24748 is an international standard that provides guidance on the application and management of systems and software life cycle processes defined in standards such as ISO/IEC 15288.
-
D.
ISO/IEC 30170
ISO/IEC 30170 is an international standard that formally specifies the Ruby programming language.
-
E.
ISO/IEC 23270
ISO/IEC 23270 is the international standard that formally defines the C# programming language specification.
- 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: ISO/IEC 25436 Triple: [Eiffel, standardName, ISO/IEC 25436]
Generated description
ISO/IEC 25436 is the international standard that formally defines the Eiffel programming language.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: ISO/IEC 25436 Target entity description: ISO/IEC 25436 is the international standard that formally defines the Eiffel programming language.
-
A.
ISO/IEC 23273
ISO/IEC 23273 is an international standard that specifies safety requirements for hydrogen-fueled road vehicles, particularly focusing on fuel cell vehicle safety.
-
B.
ISO/IEC 23271
ISO/IEC 23271 is the international standard that defines the Common Language Infrastructure (CLI), the core runtime and execution environment underlying technologies like Microsoft .NET.
-
C.
ISO/IEC 24748
ISO/IEC 24748 is an international standard that provides guidance on the application and management of systems and software life cycle processes defined in standards such as ISO/IEC 15288.
-
D.
ISO/IEC 30170
ISO/IEC 30170 is an international standard that formally specifies the Ruby programming language.
-
E.
ISO/IEC 23270
ISO/IEC 23270 is the international standard that formally defines the C# programming language specification.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355aef21c819088f168a23f1933a6 |
completed | March 13, 2026, 12:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b61382d00481908b7c84f337b5cad7 |
completed | March 15, 2026, 2:03 a.m. |
| NEDg | Description generation | batch_69b6177d1a588190991fddf506239d22 |
completed | March 15, 2026, 2:20 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69b61b6bc1448190b30d444a821bb1a5 |
completed | March 15, 2026, 2:37 a.m. |
Created at: March 12, 2026, 11:32 p.m.