Triple
T24248903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herschel crater |
E603456
|
entity |
| Predicate | hasFractures |
P32005
|
FINISHED |
| Object | radial and concentric fractures on and around rim |
—
|
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: radial and concentric fractures on and around rim | Statement: [Herschel crater, hasFractures, radial and concentric fractures on and around rim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFractures Context triple: [Herschel crater, hasFractures, radial and concentric fractures on and around rim]
-
A.
fracture
chosen
Indicates a relationship where an object or material is broken or cracked into parts, typically due to applied stress or impact.
-
B.
hasInjuries
Indicates that an entity has sustained one or more physical or bodily injuries.
-
C.
rupturesDuring
Indicates that one event or process ruptures or breaks while another specified event or time period is occurring.
-
D.
hasSpines
Indicates that one entity possesses or is characterized by spines or spine-like structures.
-
E.
brokenIn
Indicates that an object or system has become nonfunctional or damaged while located within or inside a particular place, context, or container.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b87d03c8190a38ca0c0b65ce6fc |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:04 a.m.