Triple
T7985527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MapReduce |
E185673
|
entity |
| Predicate | dataLocalityStrategy |
P80184
|
FINISHED |
| Object | move computation to data |
—
|
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: move computation to data | Statement: [MapReduce, dataLocalityStrategy, move computation to data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataLocalityStrategy Context triple: [MapReduce, dataLocalityStrategy, move computation to data]
-
A.
hasTypeLocality
Indicates the specific geographic location where an entity (typically a species or specimen) was originally found and formally described.
-
B.
containsLocality
Indicates that one place or area geographically includes or encompasses another locality within its boundaries.
-
C.
localityCondition
Indicates a spatial or contextual constraint specifying where or under what local conditions a relationship, event, or property holds.
-
D.
favoredRegion
Indicates that one region is preferred or given special priority over others in a particular context.
-
E.
prePartitionLocation
Indicates the location of an entity before a partitioning or splitting event occurs.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:15 p.m.