Triple
T27799389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spooling Directory Source |
E702196
|
entity |
| Predicate | processingOrderOption |
P51068
|
FINISHED |
| Object | oldest |
—
|
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: oldest | Statement: [Spooling Directory Source, processingOrderOption, oldest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processingOrderOption Context triple: [Spooling Directory Source, processingOrderOption, oldest]
-
A.
processingOrder
chosen
Indicates the sequence or priority in which items, tasks, or requests are to be processed or handled.
-
B.
orderHandling
Indicates how an order is processed, managed, or fulfilled from initiation through completion.
-
C.
productionOrder
Indicates that one entity is created, manufactured, or assembled according to a formal request or plan issued by another entity.
-
D.
orderParameterOf
Indicates that one entity is an order parameter that characterizes the state or phase behavior of another entity.
-
E.
orderingType
Indicates the specific method or arrangement by which items, events, or entities are ordered or sequenced relative to one another.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 5:33 p.m.