Triple
T17517078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IronLanguages |
E426595
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | IronLanguages project |
—
|
NE NERFINISHED |
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: IronLanguages project | Statement: [IronLanguages, name, IronLanguages project]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IronLanguages project Context triple: [IronLanguages, name, IronLanguages project]
-
A.
IronLanguages project
chosen
The IronLanguages project is an open-source initiative that develops and maintains .NET implementations of dynamic programming languages such as IronPython and IronRuby.
-
B.
Mono language
Mono language is a Native American Uto-Aztecan language traditionally spoken by the Mono people of eastern California.
-
C.
Odin programming language
Odin is a statically typed, compiled systems programming language focused on simplicity, data-oriented design, and high performance as an alternative to C.
-
D.
Voltaic languages
Voltaic languages are a branch of the Niger-Congo language family spoken primarily in West Africa, especially in countries like Burkina Faso, Ghana, and Togo.
-
E.
Eiffel programming language
Eiffel is an object-oriented programming language designed by Bertrand Meyer that emphasizes software correctness through features like Design by Contract and strong support for modular, reusable code.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452615a8481909974e9855ea7a8e4 |
completed | April 19, 2026, 3:56 a.m. |
Created at: April 10, 2026, 5:49 a.m.