Triple
T3724164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSCE Permanent Council |
E81707
|
entity |
| Predicate | meetsInFormat |
P38824
|
FINISHED |
| Object | formal plenary meetings |
—
|
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: formal plenary meetings | Statement: [OSCE Permanent Council, meetsInFormat, formal plenary meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsInFormat Context triple: [OSCE Permanent Council, meetsInFormat, formal plenary meetings]
-
A.
meetsFormat
Indicates that something conforms to, satisfies, or is compliant with a specified format or structural standard.
-
B.
operatesInFormat
chosen
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
C.
hasMatchFormat
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
-
D.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
E.
hasExhibitFormat
Indicates the specific format or medium in which an exhibit is presented or made available.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf3f2ec8190a3a8f363cfb762f3 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.