Triple
T38575424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNSCOP |
E929387
|
entity |
| Predicate | heldHearingsIn |
P11604
|
FINISHED |
| Object | Palestine |
—
|
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: Palestine | Statement: [UNSCOP, heldHearingsIn, Palestine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldHearingsIn Context triple: [UNSCOP, heldHearingsIn, Palestine]
-
A.
heldPublicHearings
chosen
Indicates that formal meetings open to the public were conducted to gather input, discuss issues, or present information.
-
B.
courtHeld
Indicates that a court has formally decided, ruled, or determined a particular legal issue or question.
-
C.
heldCourtIn
Indicates that an authority or governing body formally conducted judicial or official proceedings in a particular place.
-
D.
presidedAt
Indicates that one entity held a position of authority or leadership over the proceedings or activities that took place at a specific event or location.
-
E.
heardByCourt
Indicates that a matter, case, or issue has been formally considered or examined by a court.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.