Triple
T21031383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eratosthenes (lunar crater) |
E518070
|
entity |
| Predicate | liesAt |
P32883
|
FINISHED |
| Object | transition between lunar maria and highlands |
—
|
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: transition between lunar maria and highlands | Statement: [Eratosthenes (lunar crater), liesAt, transition between lunar maria and highlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesAt Context triple: [Eratosthenes (lunar crater), liesAt, transition between lunar maria and highlands]
-
A.
liesIn
chosen
Indicates that one entity is located within the spatial, geographical, or conceptual boundaries of another entity.
-
B.
liesOnBorderOf
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
C.
liesOutside
Indicates that one entity is located entirely beyond the spatial or conceptual boundary of another entity.
-
D.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
-
E.
liesToThe
Indicates that one entity intentionally provides false or misleading information to 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc82b5348190b449d59e6cada9de |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.