Triple
T23253597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandara Mountains |
E581803
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Mora |
—
|
NE NERFINISHED |
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: Mora | Statement: [Mandara Mountains, near, Mora]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mora Context triple: [Mandara Mountains, near, Mora]
-
A.
Mora
Mora is a municipality in Portugal known for its rural Alentejo landscapes, traditional villages, and proximity to the Montargil reservoir.
-
B.
Mora
Mora is a canton in Costa Rica’s San José Province known for its rural landscapes, agricultural activities, and small-town communities.
-
C.
Mora
Mora is a small genus of large, tropical hardwood trees in the legume family, known for their dense, durable timber and occurrence in Neotropical rainforests.
-
D.
Mora
chosen
Mora is a town in northern Cameroon known as a local commercial and administrative center near the Mandara Mountains and the Nigerian border.
-
E.
Mora
Mora is a surname of Hungarian origin most notably borne by the German-Hungarian writer Terézia Mora.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193f9d904819097315c9bf031f667 |
completed | April 29, 2026, 5:15 a.m. |
Created at: April 17, 2026, 4:11 p.m.