Triple
T4922018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tharsis volcanic plateau |
E110486
|
entity |
| Predicate | majorComposition |
P59278
|
FINISHED |
| Object | basaltic lava |
—
|
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: basaltic lava | Statement: [Tharsis volcanic plateau, majorComposition, basaltic lava]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorComposition Context triple: [Tharsis volcanic plateau, majorComposition, basaltic lava]
-
A.
dominantComposition
chosen
Indicates that one entity is the primary or prevailing component, material, or element that makes up or characterizes another entity.
-
B.
majorConstituentType
Indicates the type or category of a primary or dominant component that makes up a larger whole.
-
C.
specialComposition
Indicates that one entity is composed of another in a distinctive or non-standard way, highlighting a particular or exceptional form of composition between them.
-
D.
standardComposition
Indicates that one entity is composed or constructed according to a recognized or conventional standard defined by another entity.
-
E.
majorForm
Indicates that one entity is the primary or principal form, version, or manifestation 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffc2ab08190992db2400562bcee |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.