Triple
T16777380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doomadgee |
E407760
|
entity |
| Predicate | remotenessCategory |
P5679
|
FINISHED |
| Object | very remote community |
—
|
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: very remote community | Statement: [Doomadgee, remotenessCategory, very remote community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remotenessCategory Context triple: [Doomadgee, remotenessCategory, very remote community]
-
A.
remoteness
Indicates the degree of physical or conceptual distance or isolation between entities.
-
B.
isLessUrbanizedThan
Indicates that one place has a lower degree of urban development or urban characteristics compared to another place.
-
C.
isInRuralAreaOf
Indicates that one entity is located within the rural area or countryside region associated with another entity.
-
D.
distanceCategory
chosen
Indicates the qualitative classification of how far apart two entities are from each other (e.g., near, medium, far).
-
E.
featuresRegionalProximity
Indicates that one entity is located near or in close geographic proximity to a particular region or another 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b212fc248190a8fe1124853bf16d |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.