Triple
T29618114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airy (Martian crater) |
E754917
|
entity |
| Predicate | cartographicImportance |
P34421
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Airy (Martian crater), cartographicImportance, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cartographicImportance Context triple: [Airy (Martian crater), cartographicImportance, high]
-
A.
cartographicSignificance
chosen
Indicates the importance or relevance of something within the context of mapping or geographic representation.
-
B.
cartographicUse
Indicates the way in which something is used or intended to be used within a cartographic or map-making context.
-
C.
cartographicContent
Indicates that the resource contains or is associated with map-related or cartographic information.
-
D.
cartographicNote
Indicates a note that provides additional cartographic information or commentary about a map or spatial representation.
-
E.
cartographyBy
Indicates that one entity is the creator or producer of the cartographic work (such as a map or chart) associated with another 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e227eec8190a5e5a8de8359875b |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:32 p.m.