Triple
T8221112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playa de las Vacas |
E192061
|
entity |
| Predicate | inhabitedStatus |
P45137
|
FINISHED |
| Object | uninhabited island beach |
—
|
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: uninhabited island beach | Statement: [Playa de las Vacas, inhabitedStatus, uninhabited island beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inhabitedStatus Context triple: [Playa de las Vacas, inhabitedStatus, uninhabited island beach]
-
A.
stateInhabited
Indicates that a particular state is (or was) lived in or occupied by a specified entity.
-
B.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
C.
isInhabitedRegion
Indicates that a region has living beings (such as humans or animals) residing within its boundaries.
-
D.
habitationStatusOfIsland
chosen
Indicates whether an island is inhabited, uninhabited, or otherwise characterized by a particular habitation status.
-
E.
hasPermanentHumanPopulation
Indicates that an entity consistently hosts a stable, long-term community of human residents rather than only temporary or transient occupants.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb77c782a8819086019ab6bac05749 |
completed | March 31, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:45 p.m.