Triple
T8985021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rábida Island |
E214637
|
entity |
| Predicate | hasMainLandingSite |
P86172
|
FINISHED |
| Object | red sand beach on north shore |
—
|
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: red sand beach on north shore | Statement: [Rábida Island, hasMainLandingSite, red sand beach on north shore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainLandingSite Context triple: [Rábida Island, hasMainLandingSite, red sand beach on north shore]
-
A.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
-
B.
wasLandingSiteDuring
Indicates that a location served as the landing site for a particular event, mission, or vehicle during a specified time or context.
-
C.
hasLandings
Indicates that an entity has one or more associated landing events or landing locations.
-
D.
wasLandingSiteForAstronaut
Indicates that a particular location served as the landing site for an astronaut.
-
E.
keyLandingSite
Indicates a location that serves as the primary or designated site where something (such as a vehicle, object, or mission) is intended to land or touch down.
- F. None of above. chosen
Provenance (4 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67ecc5188190a6fb4d5456893121 |
completed | April 1, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5febd0a08190b2de6fb422343001 |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:03 p.m.