Triple
T35260170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gileadite |
E1018347
|
entity |
| Predicate | associatedWithCovenantPeople |
P201876
|
FINISHED |
| Object | Israelites |
E83090
|
NE 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: Israelites | Statement: [Gileadite, associatedWithCovenantPeople, Israelites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCovenantPeople Context triple: [Gileadite, associatedWithCovenantPeople, Israelites]
-
A.
covenantAssociation
Indicates a formal, binding relationship or agreement that associates entities under shared obligations, promises, or terms.
-
B.
relatedCovenant
Indicates a relationship in which one covenant is connected to, associated with, or derived from another covenant.
-
C.
belongsToCovenantSystem
chosen
Indicates that an entity is part of, or governed by, a specific covenant system.
-
D.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
E.
linkedToCovenantTightness
Indicates that one entity is associated with, or determined by, the strictness or tightness of a covenant’s terms or conditions.
- F. None of above.
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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a380fa7ce7481909aeff46655f5371e |
completed | June 21, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.