Triple
T24516840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peñón de Alhucemas |
E606393
|
entity |
| Predicate | permanentCivilPopulation |
P28910
|
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: [Peñón de Alhucemas, permanentCivilPopulation, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentCivilPopulation Context triple: [Peñón de Alhucemas, permanentCivilPopulation, no]
-
A.
permanentPopulation
chosen
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
-
B.
permanentResidents
Indicates that one entity is a long-term, officially recognized resident of another entity (such as a place, institution, or jurisdiction).
-
C.
populationIncludes
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
D.
populationBasis
Indicates that a population measurement is based on, derived from, or defined with respect to a particular reference, criterion, or underlying basis.
-
E.
population
Indicates the total number of individuals living in or present within a specified area or group.
- 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:24 a.m.