Triple
T6517286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edomite religion |
E148296
|
entity |
| Predicate | sharesCulturalSphereWith |
P38730
|
FINISHED |
| Object | Levantine religions |
—
|
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: Levantine religions | Statement: [Edomite religion, sharesCulturalSphereWith, Levantine religions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCulturalSphereWith Context triple: [Edomite religion, sharesCulturalSphereWith, Levantine religions]
-
A.
hasCulturalRelation
chosen
Indicates a relationship in which entities are connected through shared, influencing, or interacting cultural practices, values, traditions, or expressions.
-
B.
culturallySimilarTo
Indicates that two entities share comparable cultural characteristics, practices, or values.
-
C.
sharesCountryWith
Indicates that two entities are located in, originate from, or are otherwise associated with the same country.
-
D.
sharesCultWith
Indicates that two entities belong to or participate in the same cult or cult-like religious group.
-
E.
hasDistinctCultureFrom
Indicates that the culture of one entity is different and distinguishable from the culture 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_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. |
Created at: March 27, 2026, 1:44 p.m.