Triple
T7985526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MapReduce |
E185673
|
entity |
| Predicate | faultToleranceMechanism |
P10377
|
FINISHED |
| Object | re-execution of failed tasks |
—
|
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: re-execution of failed tasks | Statement: [MapReduce, faultToleranceMechanism, re-execution of failed tasks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faultToleranceMechanism Context triple: [MapReduce, faultToleranceMechanism, re-execution of failed tasks]
-
A.
reliabilityMechanism
chosen
Indicates a mechanism or process that ensures the dependable, consistent, and correct functioning of a system or relationship.
-
B.
resolutionMechanism
Indicates the method, process, or system used to resolve a conflict, issue, or discrepancy between entities.
-
C.
backedByMechanism
Indicates that something is supported, enabled, or made possible by an underlying mechanism or system.
-
D.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
E.
mentionsMechanism
Indicates that one entity explicitly refers to or describes the mechanism, process, or causal pathway by which another entity operates or produces an effect.
- 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c4a55b881909a96133e56c0dffa |
completed | March 31, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:15 p.m.