Triple
T7985529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MapReduce |
E185673
|
entity |
| Predicate | jobOutput |
P66288
|
FINISHED |
| Object | output files in distributed file system |
—
|
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: output files in distributed file system | Statement: [MapReduce, jobOutput, output files in distributed file system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jobOutput Context triple: [MapReduce, jobOutput, output files in distributed file system]
-
A.
outputOf
chosen
Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
-
B.
projectOutcome
Indicates the resulting state, impact, or consequences produced by carrying out a project.
-
C.
resultUsage
Indicates how the outcome or result of an action, process, or event is used, applied, or consumed in relation to another entity or context.
-
D.
outputOfActor
Indicates that something is the result or product generated by a particular actor.
-
E.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
- 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.