Triple
T34285923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Struve (lunar crater) |
E879734
|
entity |
| Predicate | rimIntegrity |
P34241
|
FINISHED |
| Object | heavily degraded |
—
|
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: heavily degraded | Statement: [Struve (lunar crater), rimIntegrity, heavily degraded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rimIntegrity Context triple: [Struve (lunar crater), rimIntegrity, heavily degraded]
-
A.
integrity
Indicates that an entity or relationship maintains wholeness, consistency, and freedom from corruption or unauthorized alteration.
-
B.
rimType
Indicates the specific style or configuration of a rim associated with an object or component.
-
C.
usesIntegrityCheck
Indicates that an entity employs a mechanism to verify the integrity or correctness of data, code, or operations.
-
D.
rimRepresents
Indicates that one entity serves as a representation, model, or stand-in for another entity within a specific context or system.
-
E.
rimCondition
chosen
Indicates a condition or state that applies specifically to the rim or edge of an object or structure.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.