Triple
T33839421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apennine Mountains (Moon) |
E867318
|
entity |
| Predicate | hasNotableCraterNearby |
P96317
|
FINISHED |
| Object | Eratosthenes |
E196028
|
NE 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: Eratosthenes | Statement: [Apennine Mountains (Moon), hasNotableCraterNearby, Eratosthenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCraterNearby Context triple: [Apennine Mountains (Moon), hasNotableCraterNearby, Eratosthenes]
-
A.
hasSatelliteCrater
Indicates that one crater is a secondary or subsidiary crater associated with, and typically located near, another primary crater.
-
B.
hasOverlappingCrater
Indicates that one crater partially or fully overlaps another crater in space, sharing a common area of their surfaces.
-
C.
notableCrater
chosen
Indicates that a crater is especially prominent, significant, or well-known in relation to a particular celestial body or context.
-
D.
isNamedCraterOn
Indicates that a crater bears a specific name and is located on a particular celestial body.
-
E.
hasCrater
Indicates that one entity possesses or features a crater on its surface.
- F. None of above.
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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a020ec13d808190b41acdc31adc4191 |
completed | May 11, 2026, 5:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366ead654c8190abe9721f483eacfd |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a020d9259c08190ad0370091c23ea8a |
completed | May 11, 2026, 5:10 p.m. |
Created at: May 1, 2026, 1:47 a.m.