Triple
T20077224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsentaroy |
E499899
|
entity |
| Predicate | inhabitedLocalityCategory |
P87153
|
FINISHED |
| Object | rural locality |
—
|
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: rural locality | Statement: [Tsentaroy, inhabitedLocalityCategory, rural locality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inhabitedLocalityCategory Context triple: [Tsentaroy, inhabitedLocalityCategory, rural locality]
-
A.
isInhabitedLocalityType
chosen
Indicates that an entity is classified as a specific type of inhabited locality (such as a city, town, or village).
-
B.
inhabitedIn
Indicates that an entity lives, resides, or has its dwelling within a specified place or location.
-
C.
typeLocality
Indicates the specific geographic location where a specimen or taxon was originally found and formally described.
-
D.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
E.
hasUrbanLocalities
Indicates that an entity possesses or includes one or more urban localities within its jurisdiction or scope.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643d5238819098b7d4e4e2c8dd67 |
completed | April 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.