Triple
T380967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ada (programming language) |
E8676
|
entity |
| Predicate | reliability |
P10377
|
FINISHED |
| Object | emphasized |
—
|
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: emphasized | Statement: [Ada (programming language), reliability, emphasized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reliability Context triple: [Ada (programming language), reliability, emphasized]
-
A.
reliabilityMechanism
chosen
Indicates a mechanism or process that ensures the dependable, consistent, and correct functioning of a system or relationship.
-
B.
ability
Indicates that an entity has the capacity or power to perform a particular action or achieve a specific outcome.
-
C.
availability
Indicates that an entity is present, accessible, or ready for use or interaction by another entity.
-
D.
transportReliability
Indicates how consistently and dependably a transport service or system performs as expected over time.
-
E.
reusability
Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2c95088190a603bb1ee076ebd6 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.