Triple
T18169726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naharayim/Baqura area |
E434991
|
entity |
| Predicate | legalStatusChangeEffective |
P114921
|
FINISHED |
| Object | November 2019 |
—
|
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: November 2019 | Statement: [Naharayim/Baqura area, legalStatusChangeEffective, November 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusChangeEffective Context triple: [Naharayim/Baqura area, legalStatusChangeEffective, November 2019]
-
A.
legalStatusChangedIn
Indicates that an entity’s legal status was altered or reclassified within a specified jurisdiction, context, or time frame.
-
B.
legalStatusEvent
chosen
Indicates an event or action that changes, establishes, or affects the legal status or standing of an entity.
-
C.
legalStatusAfterEvent
Indicates the legal condition or classification an entity has as a result of a specified event or occurrence.
-
D.
legalStatusAfterEndTime
Indicates the legal status or condition that applies to an entity after a specified end time has passed.
-
E.
legalStatusEnd
Indicates the point or event at which a previously valid legal status, condition, or arrangement ceases to be in effect.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df555af081908a2f12bce6a13f56 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.