Triple
T6517331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qos |
E148297
|
entity |
| Predicate | worshipArea |
P71341
|
FINISHED |
| Object | Edomite kingdoms and territories |
—
|
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: Edomite kingdoms and territories | Statement: [Qos, worshipArea, Edomite kingdoms and territories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipArea Context triple: [Qos, worshipArea, Edomite kingdoms and territories]
-
A.
worshipCenter
Indicates that one entity serves as a place or facility where another entity engages in religious worship or related spiritual activities.
-
B.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
C.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
D.
worshipLevel
Indicates the degree or intensity to which one entity reveres, honors, or performs acts of worship toward another entity.
-
E.
worshipPeriod
Indicates the time span or specific period during which an act of worship or religious devotion takes place.
- F. None of above. chosen
Provenance (4 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0ece2081909c14accef90efd7c |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:44 p.m.