Triple
T13242122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Penn |
E315304
|
entity |
| Predicate | servicePromise |
P17741
|
FINISHED |
| Object | next-day delivery on qualifying lanes |
—
|
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: next-day delivery on qualifying lanes | Statement: [New Penn, servicePromise, next-day delivery on qualifying lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servicePromise Context triple: [New Penn, servicePromise, next-day delivery on qualifying lanes]
-
A.
serviceWith
chosen
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
B.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
C.
serviceUnder
Indicates that one entity operates, functions, or is provided under the authority, management, or jurisdiction of another entity.
-
D.
serviceSystem
Indicates a relationship where one entity functions as a service system that provides, manages, or supports services for another entity.
-
E.
serviceModuleFunction
Indicates that a function is provided or performed by a specific service module within a system.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d59e84c8190a9e547d0fe26a5f9 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.