Triple
T17483700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Jordan |
E425725
|
entity |
| Predicate | includesReligiousContext |
P9028
|
FINISHED |
| Object | Biblical history |
—
|
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: Biblical history | Statement: [History of Jordan, includesReligiousContext, Biblical history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesReligiousContext Context triple: [History of Jordan, includesReligiousContext, Biblical history]
-
A.
religiousCulturalContext
chosen
Indicates the religious or cultural setting, tradition, or framework within which an entity, practice, or event occurs or is interpreted.
-
B.
typicalReligionContext
Indicates the usual or most common religious setting, tradition, or affiliation associated with an entity or situation.
-
C.
originReligionContext
Indicates the religious background or setting from which something or someone originates or is derived.
-
D.
theologicalContext
Indicates the religious or doctrinal framework, tradition, or set of beliefs within which something (such as a text, event, or concept) is interpreted or understood.
-
E.
hasReligiousSee
Indicates that one entity serves as the ecclesiastical or religious jurisdiction/seat (see) of another entity.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d06c2881909632845dd7a6b1e3 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.