Triple
T31432112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anata |
E801822
|
entity |
| Predicate | hasSeparationBarrierSection |
P94342
|
FINISHED |
| Object | Israeli West Bank barrier |
—
|
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: Israeli West Bank barrier | Statement: [Anata, hasSeparationBarrierSection, Israeli West Bank barrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeparationBarrierSection Context triple: [Anata, hasSeparationBarrierSection, Israeli West Bank barrier]
-
A.
hasSeparatedSections
Indicates that something is divided into distinct, non-continuous parts or sections.
-
B.
providesSeparationFor
chosen
Indicates that one entity serves to divide, isolate, or keep another entity apart from something else.
-
C.
hasVerticalSection
Indicates that one entity possesses or includes a distinct vertical section or segment as part of its structure or representation.
-
D.
hasSectionOn
Indicates that one entity (typically a document or resource) contains a dedicated section or part that specifically addresses or discusses another entity or topic.
-
E.
hasSectionIn
Indicates that one entity contains or includes another entity as a section or subdivision within it.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: April 30, 2026, 8:58 p.m.