Triple
T35871562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSCE Special Monitoring Mission to Ukraine |
E1037238
|
entity |
| Predicate | reportingFormat |
P94383
|
FINISHED |
| Object | daily reports |
—
|
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: daily reports | Statement: [OSCE Special Monitoring Mission to Ukraine, reportingFormat, daily reports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportingFormat Context triple: [OSCE Special Monitoring Mission to Ukraine, reportingFormat, daily reports]
-
A.
reportsFormat
chosen
Indicates that one entity reports or presents information in a particular format specified by another entity.
-
B.
reportingStyle
Indicates the manner or approach an entity uses when presenting or communicating information, such as tone, structure, or level of detail in its reports.
-
C.
reportType
Indicates the specific category or kind of report associated with an entity or action.
-
D.
standardForReporting
Indicates that something is used as the accepted or prescribed basis, format, or reference for reporting information or results.
-
E.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:06 p.m.