Triple
T3551614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verkhoyansk |
E75122
|
entity |
| Predicate | permanentlyInhabited |
P8838
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Verkhoyansk, permanentlyInhabited, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentlyInhabited Context triple: [Verkhoyansk, permanentlyInhabited, true]
-
A.
hasPermanentHumanPopulation
chosen
Indicates that an entity consistently hosts a stable, long-term community of human residents rather than only temporary or transient occupants.
-
B.
periodOfContinuousInhabitation
Indicates a span of time during which a place is continuously inhabited without interruption.
-
C.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
D.
inhabitedSince
Indicates that a place has been continuously or initially occupied or lived in by someone or something starting from a specified time.
-
E.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfd52f44819088e07139fe987e2a |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.