Triple
T23016804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mare Crisium |
E573050
|
entity |
| Predicate | surfaceModifiedBy |
P38840
|
FINISHED |
| Object | volcanic flooding |
—
|
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: volcanic flooding | Statement: [Mare Crisium, surfaceModifiedBy, volcanic flooding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceModifiedBy Context triple: [Mare Crisium, surfaceModifiedBy, volcanic flooding]
-
A.
surfaceOperation
Indicates an operation or activity that is performed on or at the surface of an object, material, or environment.
-
B.
surfaceChange
chosen
Indicates a change in the physical surface characteristics or condition of an entity over time or due to some event or interaction.
-
C.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
D.
surfaceFormedBy
Indicates that a surface is created, shaped, or defined as a result of a particular process, interaction, or set of contributing factors.
-
E.
surfaceBehavior
Indicates how an entity behaves or interacts specifically at or on its surface.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e59a1c8190b8048a399a4727cb |
completed | April 29, 2026, 4:07 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:52 p.m.