Triple
T35384857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hevelius crater |
E1022758
|
entity |
| Predicate | rimCharacteristic |
P182908
|
FINISHED |
| Object | heavily eroded |
—
|
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 eroded | Statement: [Hevelius crater, rimCharacteristic, heavily eroded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rimCharacteristic Context triple: [Hevelius crater, rimCharacteristic, heavily eroded]
-
A.
rimType
Indicates the specific style or configuration of a rim associated with an object or component.
-
B.
ribCharacteristic
Indicates that a specified characteristic or property is associated with a rib.
-
C.
notableRaceCharacteristic
Indicates that an entity is distinguished by a particular race-related trait or attribute that is especially prominent or noteworthy.
-
D.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an entity.
-
E.
spanCharacteristic
Indicates that one entity has a particular measurable or descriptive property that characterizes the extent, duration, or range of another entity or phenomenon.
- F. None of above. chosen
Provenance (4 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f794f50080819095ff3c2cefc74fea |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.