Triple
T37262146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Denison |
E924283
|
entity |
| Predicate | collectiveLocalityName |
P39103
|
FINISHED |
| Object | Dongara-Port Denison |
—
|
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: Dongara-Port Denison | Statement: [Port Denison, collectiveLocalityName, Dongara-Port Denison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveLocalityName Context triple: [Port Denison, collectiveLocalityName, Dongara-Port Denison]
-
A.
collectivelyLocatedIn
Indicates that multiple entities are all located within the same place or spatial region considered as a group.
-
B.
addressLocality
Indicates the city, town, or locality in which an address is situated.
-
C.
localityOf
Indicates that one entity is the specific place, area, or locality in which another entity is situated or occurs.
-
D.
formsLocalityWith
chosen
Indicates that two or more entities together constitute or define a specific locality or local area.
-
E.
associatedWithLocality
Indicates a relationship where something has a connection or relevance to a specific geographic place or locality.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 3, 2026, 4:15 p.m.