Triple
T16668932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vernadsky crater |
E405053
|
entity |
| Predicate | isNamedForField |
P17009
|
FINISHED |
| Object | geochemistry |
—
|
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: geochemistry | Statement: [Vernadsky crater, isNamedForField, geochemistry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedForField Context triple: [Vernadsky crater, isNamedForField, geochemistry]
-
A.
namedForField
chosen
Indicates that one entity is named after, or in honor of, a particular field, discipline, or area of study.
-
B.
fieldNamedFor
Indicates that a particular field (such as a sports field or open area) bears the name of a specified person, group, or entity in their honor.
-
C.
isNamedFor
Indicates that one entity bears its name in honor of, or derived from, another entity.
-
D.
isNamedEntity
Indicates that the subject is recognized as a named entity, such as a specific person, organization, location, or other proper noun.
-
E.
isNamedUnit
Indicates that an entity is a unit of measurement that has an explicit, conventional name rather than being expressed purely in derived or composite form.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9fa3d081909457b1bdea1d96e0 |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.