Triple
T33839747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archimedes (lunar crater) |
E867325
|
entity |
| Predicate | rimElevationRelativeToFloor |
P164833
|
FINISHED |
| Object | about 2 km |
—
|
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: about 2 km | Statement: [Archimedes (lunar crater), rimElevationRelativeToFloor, about 2 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rimElevationRelativeToFloor Context triple: [Archimedes (lunar crater), rimElevationRelativeToFloor, about 2 km]
-
A.
elevationRelativeToFloor
Indicates the vertical distance or height of an entity measured relative to the floor level.
-
B.
elevationRelativeToWalls
Indicates the vertical position of an entity in relation to the height or level of surrounding walls.
-
C.
hasFloorElevation
Indicates that one entity has a specified vertical height or level above a reference point (such as sea level or ground) for its floor.
-
D.
elevationRelativeToBasilicaFloor
Indicates the vertical height or depth of something measured relative to the level of the basilica’s floor.
-
E.
elevationAtRim
chosen
Indicates the elevation value measured specifically at the rim or edge of a geographic or topographic feature.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7004e55988190a2d35d4a95a34610 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.