Triple
T3092727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanovka |
E64519
|
entity |
| Predicate | currentStateFormation |
P45865
|
FINISHED |
| Object | independent Ukraine |
—
|
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: independent Ukraine | Statement: [Yanovka, currentStateFormation, independent Ukraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentStateFormation Context triple: [Yanovka, currentStateFormation, independent Ukraine]
-
A.
onFormation
Indicates that one entity is located on or attached to the surface of a formation (such as a geological or structural feature).
-
B.
containsFormation
Indicates that one entity spatially or structurally includes or encloses a formation as part of its extent or composition.
-
C.
stateBeforeFormation
Indicates a relationship where one state or condition existed prior to the formation or creation of another entity or state.
-
D.
supportedFormation
Indicates that one entity provided assistance, resources, or conditions that enabled the creation or establishment of another entity or structure.
-
E.
stateForm
Indicates that an entity has the political or constitutional form of a particular state or system of government.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada21055b88190b602425a513af7e6 |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.