Triple
T26585937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Sistova |
E667209
|
entity |
| Predicate | treatyArticleCount |
P165046
|
FINISHED |
| Object | 29 articles |
—
|
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: 29 articles | Statement: [Treaty of Sistova, treatyArticleCount, 29 articles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyArticleCount Context triple: [Treaty of Sistova, treatyArticleCount, 29 articles]
-
A.
treatyNumber
Indicates the specific identifying number assigned to a treaty within a legal or diplomatic framework.
-
B.
numberOfCoreTreaties
Indicates the total count of fundamental or primary treaties associated with a given entity or context.
-
C.
resultOfTreaties
Indicates that something exists, occurs, or holds true as a consequence or outcome of one or more treaties.
-
D.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
E.
treatyFamily
Indicates that there exists a familial or kinship-based treaty or formal agreement relationship between the entities.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 2:05 a.m.