Triple
T2446916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimmeridgian limestone |
E53614
|
entity |
| Predicate | soilDerivedFrom |
P2051
|
FINISHED |
| Object | limestone scree |
—
|
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: limestone scree | Statement: [Kimmeridgian limestone, soilDerivedFrom, limestone scree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soilDerivedFrom Context triple: [Kimmeridgian limestone, soilDerivedFrom, limestone scree]
-
A.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
B.
soilPreference
Indicates the type or condition of soil that an entity prefers or is best suited to grow or exist in.
-
C.
sedimentSource
chosen
Indicates that one entity serves as the origin or provider of sediment that is transported to or deposited in another entity.
-
D.
receivesMoistureFrom
Indicates that one entity obtains or is supplied with moisture (such as water, humidity, or precipitation) from another entity.
-
E.
excavatedFrom
Indicates that something (typically an artifact, fossil, or material) was dug out or uncovered from a specific location or source through excavation.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.