Triple
T31503237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acasta Gneiss Complex |
E803743
|
entity |
| Predicate | surfaceExposure |
P99309
|
FINISHED |
| Object | small 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: small outcrops | Statement: [Acasta Gneiss Complex, surfaceExposure, small outcrops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceExposure Context triple: [Acasta Gneiss Complex, surfaceExposure, small outcrops]
-
A.
exposureLevel
chosen
Indicates the degree or intensity to which an entity is subjected or exposed to a particular factor, condition, or influence.
-
B.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
C.
surfaceExpressionOf
Indicates that one entity is a specific surface-level manifestation or observable form of another underlying entity or concept.
-
D.
surfaceCover
Indicates that one entity forms the material or layer that covers the outer surface of another entity.
-
E.
surfaceCurrent
Indicates that one entity is the prevailing flow or movement of a fluid (such as water or air) along the surface of another entity.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a214a24481908d30547f6d36aabe |
completed | May 3, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:45 p.m.