Triple
T34988402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tintagel Old Post Office |
E1009314
|
entity |
| Predicate | operatedAsPostOfficeUntil |
P6603
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Tintagel Old Post Office, operatedAsPostOfficeUntil, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsPostOfficeUntil Context triple: [Tintagel Old Post Office, operatedAsPostOfficeUntil, late 19th century]
-
A.
postalFunctionCeased
Indicates that a postal service or function that once operated at a location or entity has been discontinued or is no longer in effect.
-
B.
operatedPostOfficesIn
Indicates that one entity managed and ran the functioning of post office locations within the domain or area of another entity.
-
C.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
D.
hadPostOfficeEstablished
Indicates that a post office was officially created or began operating at a given location or for a given entity.
-
E.
hadPostOffice
Indicates that a place or entity possessed or was served by an official post office facility.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a011d76f3f88190be3d7c9eb0552f34 |
completed | May 11, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_6a011cce684881909dd15776bb77a6e0 |
completed | May 11, 2026, 12:03 a.m. |
Created at: May 3, 2026, 4:01 p.m.