Triple
T2964129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israel |
E80119
|
entity |
| Predicate | makesVowTo |
P23834
|
FINISHED |
| Object | God at Bethel |
—
|
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: God at Bethel | Statement: [Israel, makesVowTo, God at Bethel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: makesVowTo Context triple: [Israel, makesVowTo, God at Bethel]
-
A.
primaryVows
Indicates that an entity has made or is bound by its main or foundational vows, promises, or commitments in a given context.
-
B.
tookReligiousVows
Indicates that an entity formally committed to a religious life by taking recognized vows within a religious tradition.
-
C.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
D.
tookReligiousVowsOn
Indicates that an entity formally committed to religious vows on a specific date or occasion.
-
E.
hasVow
chosen
Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9958b1e48190a77f37bf63333c5b |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.