Triple
T1160412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ReasonML |
E24477
|
entity |
| Predicate | hasStrongGuarantee |
P2194
|
FINISHED |
| Object | 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: type safety | Statement: [ReasonML, hasStrongGuarantee, type safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongGuarantee Context triple: [ReasonML, hasStrongGuarantee, type safety]
-
A.
deliveryGuarantee
Indicates that one party commits to ensuring that an item, service, or outcome will be delivered under specified conditions or within a defined timeframe.
-
B.
orderingGuarantee
Indicates that there is a constraint on the relative order in which related events, operations, or messages must occur or be observed.
-
C.
ensures
chosen
Indicates that one entity guarantees or makes certain that a particular condition, outcome, or state holds for another entity or situation.
-
D.
hasStrongCurrent
Indicates that one entity (typically a body of water or medium) possesses a powerful, fast-moving flow or current relative to a reference point or standard.
-
E.
hasMandate
Indicates that an entity is officially authorized or required to perform a specific role, action, or set of responsibilities.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcaf3a9081908bad2eba74dffbc1 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.