Triple
T8180383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Zboriv |
E191044
|
entity |
| Predicate | stipulatedCossackRegisterSize |
P13942
|
FINISHED |
| Object | 40000 |
—
|
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: 40000 | Statement: [Treaty of Zboriv, stipulatedCossackRegisterSize, 40000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stipulatedCossackRegisterSize Context triple: [Treaty of Zboriv, stipulatedCossackRegisterSize, 40000]
-
A.
militarySize
Indicates the total number of personnel in a military force, typically including active-duty members and sometimes reserves.
-
B.
garrisonSize
Indicates the number of troops or defenders stationed at a particular location as its garrison.
-
C.
restrictedArmySizeOf
chosen
Indicates that one entity imposes a limitation or cap on the allowable size of another entity’s army.
-
D.
stateSize
Indicates the relative or absolute physical extent or dimensions of a state, such as its area or population size.
-
E.
regimentalNumber
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
- 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4ac012948190bb4e2448561692e6 |
completed | March 31, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.