Triple
T22932140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESummary |
E569468
|
entity |
| Predicate | supportsBatchRequests |
P86209
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ESummary, supportsBatchRequests, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBatchRequests Context triple: [ESummary, supportsBatchRequests, true]
-
A.
supportsBatchProcessing
chosen
Indicates that the subject can handle multiple items or tasks in a single grouped operation rather than processing them individually.
-
B.
supportsBatchScheduler
Indicates that an entity provides functionality or compatibility for executing tasks via a batch scheduling system.
-
C.
supportsDynamicBatching
Indicates that an entity is capable of handling or processing variable-sized batches of items or requests at runtime, rather than requiring a fixed batch size.
-
D.
supportsMultipleLayersPerRequest
Indicates that a single request can handle or process multiple layers at the same time.
-
E.
supportsMultipleObjects
Indicates that the relationship or action can simultaneously involve or apply to more than one object at the same time.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1813260608190bb9e1ca704c7e12f |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:44 p.m.