Triple
T3976023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supai, Arizona |
E85643
|
entity |
| Predicate | mailDeliveryMethod |
P10739
|
FINISHED |
| Object | pack mule |
—
|
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: pack mule | Statement: [Supai, Arizona, mailDeliveryMethod, pack mule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mailDeliveryMethod Context triple: [Supai, Arizona, mailDeliveryMethod, pack mule]
-
A.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
B.
deliveryMode
chosen
Indicates the method or channel through which something (such as a product, service, or information) is delivered or provided.
-
C.
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.
-
D.
attachmentMethod
Indicates the way or technique by which one entity is fastened, joined, or secured to another.
-
E.
postalIntegration
Indicates a relationship where one system or entity is connected to and can exchange or synchronize data with a postal or mail-handling 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.