Triple
T37331767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uliga |
E926769
|
entity |
| Predicate | partOfUrbanCluster |
P294
|
FINISHED |
| Object | Delap-Uliga-Djarrit |
—
|
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: Delap-Uliga-Djarrit | Statement: [Uliga, partOfUrbanCluster, Delap-Uliga-Djarrit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfUrbanCluster Context triple: [Uliga, partOfUrbanCluster, Delap-Uliga-Djarrit]
-
A.
isUrbanLocality
Indicates that a place is classified as an urban settlement or locality, as opposed to a rural area.
-
B.
relatedUrbanArea
Indicates that one urban area is geographically or functionally associated with another urban area, such as being nearby, connected, or part of the same broader metropolitan context.
-
C.
partOfMetropolitanArea
chosen
Indicates that one place is included within and belongs to the larger metropolitan area of another place.
-
D.
isUrbanSectionOf
Indicates that one area or segment is the part of a larger entity that lies within an urban or city environment.
-
E.
isUrbanExtensionOf
Indicates that one urban area serves as a spatial or functional continuation or outward expansion of another urban area.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a016336c58081909c58c5772e6fb488 |
completed | May 11, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a0160f25d8081909a6aaa375e9850b0 |
completed | May 11, 2026, 4:54 a.m. |
Created at: May 3, 2026, 4:16 p.m.