Triple
T15837725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Bila Tserkva (1651) |
E384025
|
entity |
| Predicate | limitedRegisteredCossacksTo |
P13942
|
FINISHED |
| Object | 20,000 |
—
|
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: 20,000 | Statement: [Treaty of Bila Tserkva (1651), limitedRegisteredCossacksTo, 20,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedRegisteredCossacksTo Context triple: [Treaty of Bila Tserkva (1651), limitedRegisteredCossacksTo, 20,000]
-
A.
restrictedArmySizeOf
chosen
Indicates that one entity imposes a limitation or cap on the allowable size of another entity’s army.
-
B.
limitedMembershipTo
Indicates that access, participation, or inclusion in something is restricted to a specific subset of entities or members.
-
C.
limitedIssueOf
Indicates that one entity is issued or made available in a restricted or finite quantity by another entity.
-
D.
restrictsPowerOf
Indicates that one entity limits, constrains, or reduces the authority, control, or influence that another entity can exercise.
-
E.
limitedNumberOfMembers
Indicates that the associated group or entity has a maximum allowed number of members or participants.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e3d48c8190ad0d0af89d062101 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.