Triple
T5412508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copernicus (lunar crater) |
E121044
|
entity |
| Predicate | raySystemExtent |
P22930
|
FINISHED |
| Object | over 800 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: over 800 km | Statement: [Copernicus (lunar crater), raySystemExtent, over 800 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raySystemExtent Context triple: [Copernicus (lunar crater), raySystemExtent, over 800 km]
-
A.
raySystemAppearance
Indicates the visual characteristics or presentation style of a ray-based system (such as its look, layout, or display properties).
-
B.
maximumExtent
chosen
Indicates the greatest or furthest degree, size, or range to which something can extend or apply within a given context.
-
C.
eezExtent
Indicates the geographic area or spatial coverage of a country's exclusive economic zone (EEZ).
-
D.
raySystemAge
Indicates the age or time duration for which a ray system has existed or been in effect.
-
E.
numberOfRays
Indicates the count of rays associated with or emitted by a given entity.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bb3c0c81908711784bc865ff03 |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.