Triple
T605075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaver Island |
E11576
|
entity |
| Predicate | hasPermanentPopulation |
P8838
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Beaver Island, hasPermanentPopulation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPermanentPopulation Context triple: [Beaver Island, hasPermanentPopulation, yes]
-
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.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
C.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
D.
governedPopulation
Indicates that one entity serves as the governing authority over the population of another entity.
-
E.
populationIncludes
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
- 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df34abc8190a578c8c2ab3d28e4 |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cf8fc1c81908a9c7df552aa1a59 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.