Triple
T24506039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Lewis |
E618069
|
entity |
| Predicate | geologyRegion |
P42212
|
FINISHED |
| Object | Basin and Range Province |
—
|
NE NERFINISHED |
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: Basin and Range Province | Statement: [Mount Lewis, geologyRegion, Basin and Range Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologyRegion Context triple: [Mount Lewis, geologyRegion, Basin and Range Province]
-
A.
regionalGeologyContext
Indicates the broader geological setting or framework within which a specific geological feature, event, or observation occurs.
-
B.
geologicalOriginRegion
Indicates the geographic region from which a geological feature, material, or formation originally derives.
-
C.
naturalRegionOf
Indicates that one entity is the natural geographic region or area in which the other entity is located or to which it belongs.
-
D.
planetRegion
Indicates that a specified region or area is located on or associated with a particular planet.
-
E.
geologicalProvinceOf
chosen
Indicates that one entity is the geological province to which another entity (such as a region or feature) belongs or is classified.
- 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_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:23 a.m.