Triple
T8644983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Teschen |
E204750
|
entity |
| Predicate | limitedClaimsOf |
P99
|
FINISHED |
| Object | Austria on Bavarian territories |
—
|
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: Austria on Bavarian territories | Statement: [Treaty of Teschen, limitedClaimsOf, Austria on Bavarian territories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedClaimsOf Context triple: [Treaty of Teschen, limitedClaimsOf, Austria on Bavarian territories]
-
A.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
B.
limitaCon
Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
-
C.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
D.
uniqueClaim
Indicates that a claim is distinct and not duplicated or shared with any other claim in the given context.
-
E.
claimsToContinue
Indicates that one entity asserts or promises that an action, state, or relationship will persist into the future.
- 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_69ca834ca1c88190a11ffb0200342fac |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc479999c881908c0c4e01c07d02d4 |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:28 p.m.