Triple
T24684630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabbok |
E611246
|
entity |
| Predicate | historicallyBordered |
P47008
|
FINISHED |
| Object | Ammon |
—
|
NE NERFINISHED |
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: Ammon | Statement: [Jabbok, historicallyBordered, Ammon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyBordered Context triple: [Jabbok, historicallyBordered, Ammon]
-
A.
borderHistory
Indicates the historical changes, events, or status of borders between entities over time.
-
B.
historicallyCircumscribedBy
Indicates that one entity’s historical existence, development, or significance is bounded, defined, or delimited by the historical context or period associated with another entity.
-
C.
historicallyEncompassed
Indicates that one entity previously included, covered, or contained another entity within its scope, extent, or boundaries during a past historical period.
-
D.
historicBoundaryFor
chosen
Indicates that one entity serves as a historical boundary or border associated with another entity, typically reflecting past territorial or administrative limits.
-
E.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 3:17 a.m.