Triple
T31384467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gettysburg–Newark Lowland section |
E800558
|
entity |
| Predicate | hasSoilDerivedFrom |
P48944
|
FINISHED |
| Object | weathered sedimentary rocks |
—
|
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: weathered sedimentary rocks | Statement: [Gettysburg–Newark Lowland section, hasSoilDerivedFrom, weathered sedimentary rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoilDerivedFrom Context triple: [Gettysburg–Newark Lowland section, hasSoilDerivedFrom, weathered sedimentary rocks]
-
A.
soilOrigin
chosen
Indicates the source or provenance from which a given soil was formed or obtained.
-
B.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
C.
soilRepresents
Indicates that one soil sample, type, or condition stands for, symbolizes, or serves as a proxy for another soil-related state or concept.
-
D.
hasSoilProperty
Indicates that a soil entity possesses or is characterized by a specific soil-related property or attribute.
-
E.
hasSoilTexture
Indicates that one entity (typically a soil or land area) possesses a specific soil texture classification (such as sandy, loamy, or clayey).
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 29, 2026, 9:19 p.m.