Triple
T27927536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadoop MapReduce v1 JobTracker |
E707878
|
entity |
| Predicate | scalesPoorlyBeyond |
P22686
|
FINISHED |
| Object | several thousand nodes |
—
|
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: several thousand nodes | Statement: [Hadoop MapReduce v1 JobTracker, scalesPoorlyBeyond, several thousand nodes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scalesPoorlyBeyond Context triple: [Hadoop MapReduce v1 JobTracker, scalesPoorlyBeyond, several thousand nodes]
-
A.
scalability
chosen
Indicates the capacity of a system, process, or solution to handle increasing amounts of work, users, or data by efficiently expanding its resources or performance.
-
B.
coversScale
Indicates that one entity spans, includes, or applies across the full range or extent of another entity’s scale.
-
C.
wasScaledFor
Indicates that something was adjusted in size, capacity, or extent to suit a particular context, requirement, or target.
-
D.
predictsPoorly
Indicates that one entity makes predictions about another entity or outcome with low accuracy or reliability.
-
E.
extendsBeyond
Indicates that one entity continues past or surpasses the spatial, temporal, or conceptual limits of 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:01 p.m.