Triple
T27131552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McDelivery |
E681574
|
entity |
| Predicate | deliveryLocationType |
P117734
|
FINISHED |
| Object | office |
—
|
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: office | Statement: [McDelivery, deliveryLocationType, office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliveryLocationType Context triple: [McDelivery, deliveryLocationType, office]
-
A.
locationOfDelivery
Indicates the place or address where an item, service, or shipment is to be delivered.
-
B.
deliveryPointType
chosen
Indicates the specific kind or category of location where a delivery is intended to be made.
-
C.
deliveryType
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
-
D.
deliverySystem
Indicates a system, method, or mechanism by which something (such as a product, service, or substance) is transported, distributed, or conveyed from a source to a recipient.
-
E.
deliveryEnvironment
Indicates the context or conditions under which a delivery takes place, such as location, medium, or surrounding circumstances of the delivery 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 9:04 a.m.