Triple
T3500346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern England Chalk Formation |
E73949
|
entity |
| Predicate | erosionStyle |
P38602
|
FINISHED |
| Object | forms dry valleys |
—
|
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: forms dry valleys | Statement: [Southern England Chalk Formation, erosionStyle, forms dry valleys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: erosionStyle Context triple: [Southern England Chalk Formation, erosionStyle, forms dry valleys]
-
A.
hasErosionFeature
chosen
Indicates that one entity exhibits or contains a specific erosion-related feature or form resulting from erosional processes.
-
B.
deformationStyle
Indicates the manner or pattern in which an object or material is deformed under applied forces or conditions.
-
C.
typicalBlendStyle
Indicates the usual or characteristic way in which two or more elements are combined or mixed together.
-
D.
featuresStyle
Indicates that one entity exhibits, incorporates, or is characterized by a particular style associated with another entity.
-
E.
editingStyle
Indicates the characteristic manner or approach used when revising, arranging, or refining content.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbd4eb308190b84e84261ceec229 |
completed | March 8, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.