Triple
T11391414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terézia Mora |
E269846
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Mora |
E269846
|
NE 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: Mora | Statement: [Terézia Mora, familyName, Mora]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mora Context triple: [Terézia Mora, familyName, Mora]
-
A.
Mora
Mora is a town in central Sweden’s Dalarna region, known for its traditional Swedish culture, proximity to Lake Siljan, and as the finish line of the Vasaloppet cross-country ski race.
-
B.
Mora
Mora is a municipality in Portugal known for its rural Alentejo landscapes, traditional villages, and proximity to the Montargil reservoir.
-
C.
Mora
Mora is a canton in Costa Rica’s San José Province known for its rural landscapes, agricultural activities, and small-town communities.
-
D.
Mora
chosen
Mora is a surname of Hungarian origin most notably borne by the German-Hungarian writer Terézia Mora.
-
E.
Daulian
Daulian refers to an inhabitant or native of the ancient Greek town of Daulis in Phocis.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d8001796f48190822526f52e3f0337 |
completed | April 9, 2026, 7:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5b813cfc48190a10d9b78953112ae |
completed | April 20, 2026, 5:22 a.m. |
Created at: April 8, 2026, 9:34 p.m.