Triple
T20276684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geology of Kent |
E503033
|
entity |
| Predicate | includesLandform |
P940
|
FINISHED |
| Object | chalk downs |
—
|
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: chalk downs | Statement: [Geology of Kent, includesLandform, chalk downs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLandform Context triple: [Geology of Kent, includesLandform, chalk downs]
-
A.
hasLandform
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
B.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
-
C.
hasLandformOrigin
Indicates that something originates from, or is formed by, a particular landform.
-
D.
connectsLandform
Indicates a relationship where one landform serves as a physical link or passage between two or more other landforms.
-
E.
createsLandform
Indicates that one entity brings about the formation or existence of a physical landform in relation to another entity.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e675e3df68819096fb859bc92a0da1 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:35 a.m.