Triple
T13050647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jephthah |
E327438
|
entity |
| Predicate | testedTribe |
P108448
|
FINISHED |
| Object | Ephraimites at the fords of the Jordan |
—
|
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: Ephraimites at the fords of the Jordan | Statement: [Jephthah, testedTribe, Ephraimites at the fords of the Jordan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testedTribe Context triple: [Jephthah, testedTribe, Ephraimites at the fords of the Jordan]
-
A.
introducedTribe
Indicates that one entity caused a tribe to become known, present, or established to another entity or context for the first time.
-
B.
includesTribe
Indicates that one entity contains, encompasses, or has within it a particular tribe as a member or component.
-
C.
recognizedTribe
Indicates that a group is officially acknowledged as a tribe by a governing or authoritative body.
-
D.
triedBy
Indicates that an entity has made an attempt to perform an action on, or in relation to, another entity.
-
E.
tribeInteractedWith
Indicates that a tribe has engaged in some form of interaction or contact with another entity.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
| PDg | Predicate description generation | batch_69d98a9577d081908ddef9ea77e408e2 |
completed | April 10, 2026, 11:41 p.m. |
Created at: April 9, 2026, 8:57 p.m.