Triple
T34643590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea of Knowledge |
E889634
|
entity |
| Predicate | hasGeologicUnitType |
P50412
|
FINISHED |
| Object | mare basalt unit |
—
|
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: mare basalt unit | Statement: [Sea of Knowledge, hasGeologicUnitType, mare basalt unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeologicUnitType Context triple: [Sea of Knowledge, hasGeologicUnitType, mare basalt unit]
-
A.
hasGeologicalUnit
Indicates that an entity is associated with or contains a specific geological unit, such as a rock layer, formation, or stratigraphic unit.
-
B.
hasStratigraphicUnitType
Indicates that a stratigraphic unit is classified as having a specific type within a stratigraphic or geological framework.
-
C.
geologicUnitOf
Indicates that one entity is a geologic unit to which the other entity belongs or with which it is associated.
-
D.
geologicType
chosen
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
E.
hasGeologicalNature
Indicates that something possesses a specific geological character, composition, or formation type.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 1, 2026, 2:04 a.m.