Triple
T35352795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagyszentmiklós |
E1020929
|
entity |
| Predicate | afterTreaty |
P138561
|
FINISHED |
| Object | Treaty of Trianon |
—
|
NE NERFINISHED |
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: Treaty of Trianon | Statement: [Nagyszentmiklós, afterTreaty, Treaty of Trianon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterTreaty Context triple: [Nagyszentmiklós, afterTreaty, Treaty of Trianon]
-
A.
treatyAfter
Indicates that a treaty or formal agreement was established after a specified prior event, condition, or relationship between the entities.
-
B.
reformedByTreaty
Indicates that an existing entity has been reorganized or restructured as a result of the terms of a formal treaty.
-
C.
resultOfTreaties
chosen
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.
peaceTreatySigned
Indicates that a formal peace treaty has been concluded and signed between previously opposing parties, establishing agreed terms to end or prevent conflict.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:03 p.m.