Triple
T18810995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mooresville, Alabama |
E460013
|
entity |
| Predicate | postOfficeInContinuousOperationSince |
P80913
|
FINISHED |
| Object | 1840 |
—
|
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: 1840 | Statement: [Mooresville, Alabama, postOfficeInContinuousOperationSince, 1840]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postOfficeInContinuousOperationSince Context triple: [Mooresville, Alabama, postOfficeInContinuousOperationSince, 1840]
-
A.
operatedPostOfficesIn
Indicates that one entity managed and ran the functioning of post office locations within the domain or area of another entity.
-
B.
hasPostalServiceThrough
Indicates that one entity receives or provides postal services by means of, or via the infrastructure of, another entity.
-
C.
operatedSince
chosen
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
D.
operatedAt
Indicates that an operation, procedure, or activity was performed at a specific location or facility.
-
E.
legalStatusOfPostOffice
Indicates the legal status or standing of a post office within a given jurisdiction or regulatory framework.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3dc01248190ab1c8943d180ca05 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.