Triple
T35894747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lithgow region |
E1038187
|
entity |
| Predicate | postalRegionIncludes |
P32592
|
FINISHED |
| Object | Lithgow |
—
|
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: Lithgow | Statement: [Lithgow region, postalRegionIncludes, Lithgow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalRegionIncludes Context triple: [Lithgow region, postalRegionIncludes, Lithgow]
-
A.
postalRegionOf
Indicates that a given area or zone serves as the designated postal region for another location or address.
-
B.
postalAreaIncludes
chosen
Indicates that a given postal area geographically contains or covers another specified location or region.
-
C.
hasPostalAddressRegion
Indicates the region component (such as state, province, or area) associated with an entity’s postal address.
-
D.
hasPostalTerritory
Indicates that one entity possesses or is assigned a specific postal territory within a postal or mailing system.
-
E.
postalDivision
Indicates the administrative or geographic subdivision used for organizing postal services and mail delivery within a larger region.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3ce2ac81908545981edf1fafdd |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.