Triple
T37262220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abrolhos Islands |
E924284
|
entity |
| Predicate | humanPopulationType |
P5947
|
FINISHED |
| Object | seasonal fishing camps |
—
|
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: seasonal fishing camps | Statement: [Abrolhos Islands, humanPopulationType, seasonal fishing camps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanPopulationType Context triple: [Abrolhos Islands, humanPopulationType, seasonal fishing camps]
-
A.
hadPopulationType
Indicates that an entity possessed a particular classification or type of population during a given time or context.
-
B.
hasPopulationType
chosen
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
-
C.
hostsPopulation
Indicates that an entity serves as the living environment or container in which a particular population exists or resides.
-
D.
servicePopulationType
Indicates the type or category of population that a service is intended to serve or target.
-
E.
populationScale
Indicates the relative size or magnitude of a population, typically categorizing it into broad scale levels (e.g., small, medium, large).
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.