Triple
T15331719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paleozoic Plateau |
E366549
|
entity |
| Predicate | hasSurfaceExposure |
P27395
|
FINISHED |
| Object | bedrock outcrops |
—
|
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: bedrock outcrops | Statement: [Paleozoic Plateau, hasSurfaceExposure, bedrock outcrops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceExposure Context triple: [Paleozoic Plateau, hasSurfaceExposure, bedrock outcrops]
-
A.
hasSurfaceLevel
Indicates that one entity possesses or is characterized by a particular degree or measure of surface level (e.g., depth, detail, or superficiality).
-
B.
visibleAtSurface
chosen
Indicates that something can be seen or is observable at the outer surface of an object or medium.
-
C.
hasSurfaceFeatureState
Indicates that an entity currently exhibits a particular condition or status of one of its surface features.
-
D.
isExposed
Indicates that an entity is subjected or open to the influence, effects, or presence of another entity or condition.
-
E.
hasSurfaceConnections
Indicates that one entity is linked to another through connections or interfaces that occur at or across their surfaces.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e0268608190947a58f559a67717 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.