Triple
T23766405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Obadiah |
E587390
|
entity |
| Predicate | addressesPeople |
P265
|
FINISHED |
| Object | descendants of Esau |
—
|
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: descendants of Esau | Statement: [Book of Obadiah, addressesPeople, descendants of Esau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesPeople Context triple: [Book of Obadiah, addressesPeople, descendants of Esau]
-
A.
addressSystem
Indicates a relationship where an entity uses or is organized according to a particular addressing scheme or system (such as postal, IP, or other structured address formats).
-
B.
addresses
chosen
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
C.
addressesChallenge
Indicates that one entity takes action to confront, deal with, or resolve a specific challenge associated with another entity or situation.
-
D.
addressesPosition
Indicates that one entity communicates with, responds to, or deals with the role, status, or job position held by another entity.
-
E.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c462ad348190b51bcaf66715a950 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:15 p.m.