Triple
T30694655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soanian Paleolithic culture sites |
E781423
|
entity |
| Predicate | foundInLandform |
P30683
|
FINISHED |
| Object | terrace deposits |
—
|
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: terrace deposits | Statement: [Soanian Paleolithic culture sites, foundInLandform, terrace deposits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInLandform Context triple: [Soanian Paleolithic culture sites, foundInLandform, terrace deposits]
-
A.
locatedInGeographicFeature
chosen
Indicates that something is situated within or on a specific natural geographic feature (such as a mountain, river, valley, or lake).
-
B.
foundInElevation
Indicates that something exists, occurs, or is located at a particular elevation or height above a reference level.
-
C.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
D.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
E.
situatedAmong
Indicates that an entity is located within or surrounded by multiple other entities in its immediate environment.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 29, 2026, 8:33 p.m.