Triple
T13111306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stet, Missouri |
E310976
|
entity |
| Predicate | hasPostOfficeStatus |
P103405
|
FINISHED |
| Object | closed |
—
|
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: closed | Statement: [Stet, Missouri, hasPostOfficeStatus, closed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostOfficeStatus Context triple: [Stet, Missouri, hasPostOfficeStatus, closed]
-
A.
hasPostalServiceStatus
chosen
Indicates the current operational or service condition of a postal service for a given entity or location.
-
B.
hasPostalServiceThrough
Indicates that one entity receives or provides postal services by means of, or via the infrastructure of, another entity.
-
C.
hasPostalAgency
Indicates that one entity operates, hosts, or is served by a postal agency associated with another entity.
-
D.
hasPostalAuthority
Indicates that an entity possesses official authority or jurisdiction over postal services or mail operations for a given area or context.
-
E.
hasPostalTerritoryStatus
Indicates that an entity holds a specific official status or designation as a postal territory within a postal or administrative 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817e4f408190b77c198b4157d77a |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:05 p.m.