Triple
T31269344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balak |
E797339
|
entity |
| Predicate | locationOfReign |
P53632
|
FINISHED |
| Object | Plains of Moab |
—
|
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: Plains of Moab | Statement: [Balak, locationOfReign, Plains of Moab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfReign Context triple: [Balak, locationOfReign, Plains of Moab]
-
A.
reignLocation
chosen
Indicates the place or territory over which an entity rules or exercises sovereign authority.
-
B.
ancestralSeatOf
Indicates that one entity is the traditional or original home, origin place, or foundational location associated with the lineage, heritage, or authority of another entity.
-
C.
seatOfPowerLocatedIn
Indicates that the primary governing authority or central power base of an entity is situated within a specified location.
-
D.
capitalOfRealmDuringReign
Indicates that a particular city or place served as the capital of a realm specifically during the time span of a given ruler’s reign.
-
E.
administrativeCenterForEmpire
Indicates that a location served as the main administrative center or capital for a particular empire.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0174e8b5b481908bf0c6d3d5b0f3b6 |
completed | May 11, 2026, 6:19 a.m. |
| PD | Predicate disambiguation | batch_6a01748d65248190ac3d9adfa9d0b274 |
completed | May 11, 2026, 6:17 a.m. |
Created at: April 29, 2026, 9:13 p.m.