Triple
T32417292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolero (F# for Blazor) |
E828358
|
entity |
| Predicate | typeChecking |
P158291
|
FINISHED |
| Object | compile-time type safety |
—
|
LITERAL 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: compile-time type safety | Statement: [Bolero (F# for Blazor), typeChecking, compile-time type safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeChecking Context triple: [Bolero (F# for Blazor), typeChecking, compile-time type safety]
-
A.
checkingType
chosen
Indicates that one entity is verifying, inspecting, or assessing the type or category of another entity.
-
B.
typeCheckerName
Indicates the name or identifier assigned to a specific type checker used to validate or analyze types.
-
C.
hasTypeChecker
Indicates that an entity is associated with or utilizes a specific type checker component or mechanism.
-
D.
typings
Indicates that one entity defines or specifies the type information or type annotations associated with another entity.
-
E.
isNotType
Indicates that one entity is explicitly not of a specified type or category in relation to another.
- F. None of above.
Provenance (3 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c27cffc0819082278e7e30ae83cc |
completed | May 3, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:54 a.m.