Triple
T29641887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Union Treaty |
E755883
|
entity |
| Predicate | draftingProcessName |
P167535
|
FINISHED |
| Object | Novo-Ogarevo process |
—
|
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: Novo-Ogarevo process | Statement: [New Union Treaty, draftingProcessName, Novo-Ogarevo process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: draftingProcessName Context triple: [New Union Treaty, draftingProcessName, Novo-Ogarevo process]
-
A.
draftingStarted
Indicates that the process of creating an initial version or draft of something has begun.
-
B.
draftingAdviser
Indicates that one entity serves as an adviser responsible for drafting or preparing documents, plans, or texts for another entity.
-
C.
draftingSupervisedBy
Indicates that the drafting of a document or work product is carried out under the supervision or oversight of a specified person or authority.
-
D.
draftingBody
Indicates the entity that is responsible for formulating or composing a given document, proposal, or text.
-
E.
preDraftProcess
Indicates the procedural steps or activities that occur before a draft is created or formally written.
- F. None of above. chosen
Provenance (4 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66ed0653c819085adda918bd12f83 |
completed | May 2, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:47 p.m.