Triple
T719991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bass Rock |
E14394
|
entity |
| Predicate | hasLandingPlace |
P13117
|
FINISHED |
| Object | small landing on the southern side |
—
|
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: small landing on the southern side | Statement: [Bass Rock, hasLandingPlace, small landing on the southern side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandingPlace Context triple: [Bass Rock, hasLandingPlace, small landing on the southern side]
-
A.
hasLandings
chosen
Indicates that an entity has one or more associated landing events or landing locations.
-
B.
landedOnBy
Indicates that one entity has come down to rest upon or make contact with the surface of another entity.
-
C.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
D.
landingMethod
Indicates the manner or technique by which something or someone arrives and comes to rest at a destination, typically from the air or space.
-
E.
dateOfLanding
Indicates the specific calendar date on which a landing event took place.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58e65e8819098cba7e6a20d8f33 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f513608190b716b939d574c292 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.