Triple
T7535330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter I Island |
E178134
|
entity |
| Predicate | hasPermanentResidents |
P8838
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Peter I Island, hasPermanentResidents, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPermanentResidents Context triple: [Peter I Island, hasPermanentResidents, no]
-
A.
permanentResidents
Indicates that one entity is a long-term, officially recognized resident of another entity (such as a place, institution, or jurisdiction).
-
B.
hasResidentPopulation
Indicates that a place or administrative area has a population of people who live there permanently or for an extended period.
-
C.
permanentPopulation
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
-
D.
hasPermanentHumanPopulation
chosen
Indicates that an entity consistently hosts a stable, long-term community of human residents rather than only temporary or transient occupants.
-
E.
yearOfPermanentResidency
Indicates the specific year in which an entity began or was granted permanent residency in a particular place.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f84c13208190971096a0b81b0ff2 |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.