Triple
T19267022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crawford, Alabama |
E481810
|
entity |
| Predicate | postOfficeStatus |
P103405
|
FINISHED |
| Object | operational |
—
|
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: operational | Statement: [Crawford, Alabama, postOfficeStatus, operational]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postOfficeStatus Context triple: [Crawford, Alabama, postOfficeStatus, operational]
-
A.
postalServiceStatus
Indicates the current operational or delivery state of a postal service or mailed item (e.g., in transit, delivered, delayed).
-
B.
legalStatusOfPostOffice
Indicates the legal status or standing of a post office within a given jurisdiction or regulatory framework.
-
C.
hasPostalServiceStatus
chosen
Indicates the current operational or service condition of a postal service for a given entity or location.
-
D.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
E.
postalServiceDesignation
Indicates the official classification or label assigned to an entity by a postal service for mail handling, routing, or addressing purposes.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8d58988190a942627b1fb79285 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.