Triple
T29641888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Union Treaty |
E755883
|
entity |
| Predicate | draftedAtLocation |
P145854
|
FINISHED |
| Object | Novo-Ogaryovo residence |
—
|
NE NERFINISHED |
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-Ogaryovo residence | Statement: [New Union Treaty, draftedAtLocation, Novo-Ogaryovo residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: draftedAtLocation Context triple: [New Union Treaty, draftedAtLocation, Novo-Ogaryovo residence]
-
A.
draftedFrom
Indicates that one entity was selected or recruited from another entity, typically as part of a formal drafting or selection process.
-
B.
draftedAt
Indicates that an entity was selected or chosen by another entity at a specific draft event or position.
-
C.
draftedUnder
Indicates that one entity was formally selected or conscripted into a role, position, or service according to the authority, rules, or jurisdiction of another entity.
-
D.
draftedInCity
Indicates that an entity was formally selected or drafted while located in a particular city.
-
E.
draftedInPlace
chosen
Indicates that an entity was formally written or composed at a specific location.
- 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_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_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:47 p.m.