Triple
T7984842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apache Spark |
E185661
|
entity |
| Predicate | schedulingUnit |
P80181
|
FINISHED |
| Object | job |
—
|
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: job | Statement: [Apache Spark, schedulingUnit, job]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schedulingUnit Context triple: [Apache Spark, schedulingUnit, job]
-
A.
schedulingRule
Indicates a rule or constraint that governs when, how, or under what conditions an event or task may be scheduled.
-
B.
usedForScheduling
Indicates that something is employed to plan, arrange, or coordinate the timing of events, tasks, or activities.
-
C.
samplingUnit
Indicates that one entity serves as the basic unit or element from which samples are drawn or measured in a sampling process.
-
D.
managementUnitOf
Indicates that one entity serves as the administrative or managerial unit responsible for overseeing or controlling another entity.
-
E.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
- 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.