Triple
T6624800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interview Island |
E149766
|
entity |
| Predicate | hasInhabitationStatus |
P9067
|
FINISHED |
| Object | sparsely populated |
—
|
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: sparsely populated | Statement: [Interview Island, hasInhabitationStatus, sparsely populated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInhabitationStatus Context triple: [Interview Island, hasInhabitationStatus, sparsely populated]
-
A.
hasOccupancyStatus
Indicates the current usage or availability state of something, such as whether it is occupied, vacant, or otherwise in use.
-
B.
stateInhabited
Indicates that a particular state is (or was) lived in or occupied by a specified entity.
-
C.
hasNeighbourhoodStatus
Indicates that an entity has a particular status, classification, or condition specifically in relation to a given neighbourhood.
-
D.
hasPopulationStatus
chosen
Indicates the current demographic condition or classification of a population associated with an entity.
-
E.
residencyStatus
Indicates the legal or official residential classification of an entity within a particular jurisdiction or context.
- 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_69c687ed8a9c81908bb671717cb192ef |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:58 p.m.