Triple
T16718973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ἰδουμαῖος |
E406294
|
entity |
| Predicate | refersToRegionRelativeLocation |
P66507
|
FINISHED |
| Object | south of Judea |
—
|
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: south of Judea | Statement: [Ἰδουμαῖος, refersToRegionRelativeLocation, south of Judea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToRegionRelativeLocation Context triple: [Ἰδουμαῖος, refersToRegionRelativeLocation, south of Judea]
-
A.
refersToLocation
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
B.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
-
C.
regionReference
chosen
Indicates that one entity refers to, points to, or is associated with a specific region or area defined by another entity.
-
D.
refersToPosition
Indicates that one entity makes reference to, or is associated with, a specific position or location of another entity.
-
E.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3865855108190bf8767b7b6c5fa10 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.