Triple
T20648711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mealt Falls |
E507428
|
entity |
| Predicate | overhangs |
P140902
|
FINISHED |
| Object | sea cliffs |
—
|
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: sea cliffs | Statement: [Mealt Falls, overhangs, sea cliffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overhangs Context triple: [Mealt Falls, overhangs, sea cliffs]
-
A.
overlies
Indicates that one entity is positioned directly above and covering or resting on another entity, often with partial or complete contact.
-
B.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
-
C.
overarchedBy
Indicates that one entity is physically or conceptually spanned, covered, or dominated from above by another entity.
-
D.
holdsOver
Indicates that a certain condition, state, or relationship remains valid or continues to apply across a specified period, context, or range.
-
E.
overlooks
Indicates that one entity has a view toward or looks out over another entity, typically from a higher or adjacent position.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6af2076b48190b9c8afb4eac65f46 |
completed | April 20, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:43 a.m.