Triple
T18978965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayan Har tectonic block |
E464370
|
entity |
| Predicate | hasCrustalType |
P134015
|
FINISHED |
| Object | 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: continental crust | Statement: [Bayan Har tectonic block, hasCrustalType, continental crust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrustalType Context triple: [Bayan Har tectonic block, hasCrustalType, continental crust]
-
A.
hasCrustalContext
Indicates that something is associated with, situated within, or characterized by a particular geological crustal setting or context.
-
B.
hasCrustalThickness
Indicates the relationship in which an object or region possesses a specified thickness of its crust.
-
C.
crustType
Indicates the specific style or form of crust associated with an item, such as a pizza or baked good.
-
D.
crustTypeProduced
Indicates the type of crust that is produced as the result of a particular process, action, or production activity.
-
E.
hasCrustType
Indicates that an entity (such as a pizza or pie) is associated with a specific type or style of crust.
- F. None of above. chosen
Provenance (4 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d621e3e08190b2d1d969ecaa380b |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:01 p.m.