Triple
T28537992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matmid points |
E722219
|
entity |
| Predicate | programLanguageOptionsInclude |
P169584
|
FINISHED |
| Object | Hebrew |
—
|
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: Hebrew | Statement: [Matmid points, programLanguageOptionsInclude, Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programLanguageOptionsInclude Context triple: [Matmid points, programLanguageOptionsInclude, Hebrew]
-
A.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
-
B.
compilerLanguage
Indicates that one entity is the programming language in which a given compiler is implemented.
-
C.
programmingLanguageTarget
Indicates that one entity is the target or intended implementation language for programming-related work associated with another entity.
-
D.
programmingIncludes
Indicates that one programming-related entity contains, incorporates, or makes use of another as a part, feature, or component.
-
E.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
- F. None of above. chosen
Provenance (4 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 28, 2026, 3:33 a.m.