Triple
T3775244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNOV |
E83290
|
entity |
| Predicate | hostsMeetingsOn |
P613
|
FINISHED |
| Object | international security |
—
|
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: international security | Statement: [UNOV, hostsMeetingsOn, international security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsMeetingsOn Context triple: [UNOV, hostsMeetingsOn, international security]
-
A.
hostsEvent
chosen
Indicates that an entity organizes and provides the venue or setting for an event to take place.
-
B.
meetsVia
Indicates that two entities come into contact or interact with each other through a specified intermediary medium, channel, or mechanism.
-
C.
hostedDuring
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
-
D.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
-
E.
convenesDuring
Indicates that one entity formally gathers or brings together another entity or group during a specified time period or event.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc5ac9688190bc921cd3ba1d0580 |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.