Triple
T33839744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archimedes (lunar crater) |
E867325
|
entity |
| Predicate | IauFeatureId |
P177767
|
FINISHED |
| Object | 303 |
—
|
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: 303 | Statement: [Archimedes (lunar crater), IauFeatureId, 303]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IauFeatureId Context triple: [Archimedes (lunar crater), IauFeatureId, 303]
-
A.
GNISFeatureID
Indicates that an entity is associated with a specific identifier assigned by the U.S. Geological Survey’s Geographic Names Information System (GNIS) to uniquely reference a geographic feature.
-
B.
USGSID
Indicates a unique identifier assigned by the U.S. Geological Survey to distinguish a specific geographic or geological feature from all others.
-
C.
GNISID
Indicates that an entity is associated with a specific identifier from the U.S. Geographic Names Information System (GNIS), uniquely linking it to an official geographic feature record.
-
D.
waterbodyID
Indicates a unique identifier that links an entity to a specific body of water.
-
E.
basinFeature
Indicates that one entity is a physical feature or component located within or forming part of a basin.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:47 a.m.