Triple
T829667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Saint-Germain-en-Laye |
E17934
|
entity |
| Predicate | setArmySizeLimit |
P13942
|
FINISHED |
| Object | 30000 soldiers for Austria |
—
|
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: 30000 soldiers for Austria | Statement: [Treaty of Saint-Germain-en-Laye, setArmySizeLimit, 30000 soldiers for Austria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setArmySizeLimit Context triple: [Treaty of Saint-Germain-en-Laye, setArmySizeLimit, 30000 soldiers for Austria]
-
A.
restrictedArmySizeOf
chosen
Indicates that one entity imposes a limitation or cap on the allowable size of another entity’s army.
-
B.
garrisonSize
Indicates the number of troops or defenders stationed at a particular location as its garrison.
-
C.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
D.
setsMaximum
Indicates that one entity establishes an upper limit or maximum allowable value for another entity or quantity.
-
E.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab9b458881909aa23f0eb7cbc87f |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa79a6488190a634388e071ed9b7 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.