Triple
T30482950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Road, Oxford |
E775636
|
entity |
| Predicate | inPostalTown |
P2711
|
FINISHED |
| Object | Oxford |
—
|
NE NERFINISHED |
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: Oxford | Statement: [Richmond Road, Oxford, inPostalTown, Oxford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inPostalTown Context triple: [Richmond Road, Oxford, inPostalTown, Oxford]
-
A.
postTown
chosen
Indicates the town or locality that serves as the postal address destination for a given address or location.
-
B.
hasPostalTownStatus
Indicates that an entity holds the official designation or status of being a postal town within a postal addressing system.
-
C.
postalName
Indicates the standardized name or label used for addressing and postal purposes associated with an entity.
-
D.
postalTownIncluded
Indicates that a given postal town is included within, or associated as part of, a broader postal address or geographic area.
-
E.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687439dcc81909cf153eeecc99597 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:13 p.m.