Triple
T38575407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNSCOP |
E929387
|
entity |
| Predicate | sessionReportedTo |
P154864
|
FINISHED |
| Object | Second regular session of the UN General Assembly |
—
|
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: Second regular session of the UN General Assembly | Statement: [UNSCOP, sessionReportedTo, Second regular session of the UN General Assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sessionReportedTo Context triple: [UNSCOP, sessionReportedTo, Second regular session of the UN General Assembly]
-
A.
scoreReportedTo
Indicates that a score or result has been communicated or submitted from one party to another.
-
B.
isReportedAt
Indicates that an event, fact, or occurrence is documented or made known at a particular time, place, or reporting source.
-
C.
reportedFor
Indicates that one entity has formally notified an authority or system about another entity’s behavior, condition, or status, typically to trigger review or action.
-
D.
reportedAs
Indicates that one entity has been formally reported or flagged to another entity, typically as problematic, suspicious, or noteworthy.
-
E.
reportsSubmittedTo
chosen
Indicates that one party has delivered or filed reports to another designated recipient or authority.
- 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.