Triple
T32267303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabelle |
E824319
|
entity |
| Predicate | supportsCodeGenerationTo |
P130227
|
FINISHED |
| Object | Haskell |
E95186
|
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: Haskell | Statement: [Isabelle, supportsCodeGenerationTo, Haskell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCodeGenerationTo Context triple: [Isabelle, supportsCodeGenerationTo, Haskell]
-
A.
supportsCodeBuilder
Indicates that an entity provides compatibility with or functionality for a code-building tool or environment.
-
B.
supportsGeneration
chosen
Indicates that one entity enables, facilitates, or is compatible with the creation or production of another entity or outcome.
-
C.
supportsCodeRates
Indicates that one entity is capable of handling, processing, or operating at the specific code rates associated with another entity.
-
D.
hasGenerationCode
Indicates that an entity is associated with a specific generation code that identifies its generational category or version.
-
E.
supportsImplementationOf
Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
- F. None of above.
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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f46dd86fc819085caf60913a730e9 |
completed | June 15, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:42 a.m.