Triple
T31559617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swona |
E805223
|
entity |
| Predicate | lastPermanentResidentsLeft |
P156535
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Swona, lastPermanentResidentsLeft, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastPermanentResidentsLeft Context triple: [Swona, lastPermanentResidentsLeft, 1974]
-
A.
lastPermanentResidentsLeftInYear
chosen
Indicates the year in which the final permanent residents departed from a place or entity.
-
B.
permanentResidents
Indicates that one entity is a long-term, officially recognized resident of another entity (such as a place, institution, or jurisdiction).
-
C.
hasTemporaryResidents
Indicates that an entity currently accommodates residents who are staying there only for a limited or non-permanent period.
-
D.
permanentPopulation
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
-
E.
hasResidentPopulation
Indicates that a place or administrative area has a population of people who live there permanently or for an extended period.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:14 p.m.