Triple
T699883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First-Class Mail |
E13974
|
entity |
| Predicate | deliveryArea |
P82
|
FINISHED |
| Object | all 50 U.S. states |
—
|
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: all 50 U.S. states | Statement: [First-Class Mail, deliveryArea, all 50 U.S. states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliveryArea Context triple: [First-Class Mail, deliveryArea, all 50 U.S. states]
-
A.
areaServed
chosen
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
B.
hasServiceAreas
Indicates that an entity provides services within, or is operational across, specific geographic or functional areas.
-
C.
areaComponent
Indicates that one area is a constituent or sub-area that forms part of a larger area.
-
D.
districtBasedOn
Indicates that one district is defined, derived, or established based on the boundaries, characteristics, or structure of another entity or area.
-
E.
landingArea
Indicates that a location or surface serves as a designated area where something (such as an aircraft, object, or person) can land.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a544e3608190ac315c7aa9f88e7e |
completed | March 1, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ec8c748190b198492a0eea4445 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.