Triple
T27107238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Tennessee Seismic Zone |
E686613
|
entity |
| Predicate | crustalSetting |
P134015
|
FINISHED |
| Object | old stable continental crust |
—
|
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: old stable continental crust | Statement: [Eastern Tennessee Seismic Zone, crustalSetting, old stable continental crust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crustalSetting Context triple: [Eastern Tennessee Seismic Zone, crustalSetting, old stable continental crust]
-
A.
crustalComposition
Indicates the type and proportion of materials that make up a planet or moon’s outer solid layer (its crust).
-
B.
crustType
Indicates the specific style or form of crust associated with an item, such as a pizza or baked good.
-
C.
hasCrustalType
chosen
Indicates that an object or location is associated with a specific type or classification of crust (e.g., continental, oceanic).
-
D.
hasCrustalThickness
Indicates the relationship in which an object or region possesses a specified thickness of its crust.
-
E.
crustTypeSubducting
Indicates that one type of crust is moving beneath another plate in a subduction process.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623fef610819086a38b74d8c934b3 |
completed | May 2, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:51 a.m.