Triple
T322191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFC |
E6436
|
entity |
| Predicate | reliabilityRole |
P10377
|
FINISHED |
| Object | recover bus from error conditions |
—
|
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: recover bus from error conditions | Statement: [IFC, reliabilityRole, recover bus from error conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reliabilityRole Context triple: [IFC, reliabilityRole, recover bus from error conditions]
-
A.
reliabilityMechanism
chosen
Indicates a mechanism or process that ensures the dependable, consistent, and correct functioning of a system or relationship.
-
B.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
C.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
D.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
E.
securityRole
Indicates that an entity holds a specific security-related role, permission level, or access profile within a system or context.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.