Triple
T19387038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman province of Judea |
E484961
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Idumea |
—
|
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: Idumea | Statement: [Roman province of Judea, contains, Idumea]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Idumea Context triple: [Roman province of Judea, contains, Idumea]
-
A.
Idumea
chosen
Idumea was an ancient region south of Judea, inhabited by the Edomites and later integrated into the Hasmonean and Herodian Jewish realms.
-
B.
Iadera
Iadera is the ancient Roman and medieval Latin name for the coastal city now known as Zadar in Croatia.
-
C.
Eusa
Eusa is the Breton name for Ushant, an island off the western tip of Brittany in France known for its rugged coastline and maritime heritage.
-
D.
Uruca
Uruca is a district of San José, Costa Rica, known as an important industrial and commercial area within the capital.
-
E.
Duitama
Duitama is a Colombian city in the Andean highlands known as an important commercial and transport hub within the Boyacá region.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b418f148190972b7b46038bc744 |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.