Triple
T27927532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadoop MapReduce v1 JobTracker |
E707878
|
entity |
| Predicate | hasSinglePointOfFailure |
P3282
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hadoop MapReduce v1 JobTracker, hasSinglePointOfFailure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSinglePointOfFailure Context triple: [Hadoop MapReduce v1 JobTracker, hasSinglePointOfFailure, true]
-
A.
hasFailureProbability
Indicates that an entity is associated with a likelihood or chance that it will fail within a given context or conditions.
-
B.
hasSingle
chosen
Indicates that an entity possesses exactly one instance of a specified related entity or attribute.
-
C.
hasMultipleWorking
Indicates that an entity is associated with more than one working instance, role, or configuration simultaneously.
-
D.
hasSecondaryCenter
Indicates that an entity possesses an additional, subordinate or auxiliary center beyond its primary center.
-
E.
supportsRedundancy
Indicates that one entity provides or enables backup or failover capabilities for another to ensure continued operation if a primary component fails.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 7:01 p.m.