Triple
T19348228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribe of Gilead |
E483939
|
entity |
| Predicate | hasTerritorialIdentity |
P12355
|
FINISHED |
| Object | east of the Jordan River |
—
|
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: east of the Jordan River | Statement: [Tribe of Gilead, hasTerritorialIdentity, east of the Jordan River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerritorialIdentity Context triple: [Tribe of Gilead, hasTerritorialIdentity, east of the Jordan River]
-
A.
hasTerritorialAssociation
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
-
B.
hasRegionalIdentity
chosen
Indicates that an entity possesses or is associated with a specific regional or local identity.
-
C.
hasNationalIdentity
Indicates that an entity possesses or is associated with a particular national identity or nationality.
-
D.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
E.
hasTerritorialDimension
Indicates that something possesses or involves a spatial or territorial extent, scope, or jurisdiction.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185c95248190b1e5bb8626489767 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.