Triple
T9312948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B-root |
E224047
|
entity |
| Predicate | reliabilityRequirement |
P10377
|
FINISHED |
| Object | fault tolerant operation |
—
|
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: fault tolerant operation | Statement: [B-root, reliabilityRequirement, fault tolerant operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reliabilityRequirement Context triple: [B-root, reliabilityRequirement, fault tolerant operation]
-
A.
reliabilityMechanism
chosen
Indicates a mechanism or process that ensures the dependable, consistent, and correct functioning of a system or relationship.
-
B.
performanceRequirement
Indicates that one entity specifies or imposes a required level of performance that another entity must meet or satisfy.
-
C.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
-
D.
reliabilityRecord
Indicates that there exists a record or documentation capturing the reliability characteristics, performance, or history associated with an entity or relationship.
-
E.
typicalRequirement
Indicates that one entity is a standard or commonly expected prerequisite, condition, or necessity for another entity.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ae96e481909a1af9ea1c91f2b2 |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.