Triple
T31646909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HOL4 |
E807605
|
entity |
| Predicate | hasKernelLanguage |
P181680
|
FINISHED |
| Object | Standard ML |
—
|
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: Standard ML | Statement: [HOL4, hasKernelLanguage, Standard ML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKernelLanguage Context triple: [HOL4, hasKernelLanguage, Standard ML]
-
A.
hasKernel
Indicates that one entity functions as the kernel (core or central component) of another entity.
-
B.
hasKernelType
Indicates that an entity possesses or is associated with a specific type or classification of kernel.
-
C.
hasSubstrateLanguage
Indicates a relationship where one language serves as the underlying substrate that has influenced or shaped another language.
-
D.
hasLanguageType
Indicates that an entity is associated with a particular type or category of language (e.g., spoken, written, programming, sign).
-
E.
hasCoreLanguages
Indicates that an entity is associated with one or more primary or foundational languages that are central to its function or definition.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: April 30, 2026, 10:51 p.m.