Triple
T8889334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legal Committee |
E211624
|
entity |
| Predicate | topicHandled |
P71354
|
FINISHED |
| Object | Measures to eliminate international terrorism (legal aspects) |
—
|
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: Measures to eliminate international terrorism (legal aspects) | Statement: [Legal Committee, topicHandled, Measures to eliminate international terrorism (legal aspects)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topicHandled Context triple: [Legal Committee, topicHandled, Measures to eliminate international terrorism (legal aspects)]
-
A.
handledMatter
chosen
Indicates that an entity has dealt with, managed, or taken responsibility for a particular matter, issue, or case.
-
B.
messageHandling
Indicates how messages are received, processed, and responded to within a communication or messaging system.
-
C.
handlingProperty
Indicates that one entity specifies how another entity should be handled, processed, or treated under certain conditions.
-
D.
informationTypeHandled
Indicates that an entity is responsible for processing, managing, or dealing with a particular type or category of information.
-
E.
legacyTopic
Indicates that a topic or subject is considered outdated, superseded, or retained only for backward compatibility or historical reasons.
- 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_69ca83907954819096d52a245b635841 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc618f94108190b03248832bfe68a9 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.