Triple
T29035233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kittsee |
E737839
|
entity |
| Predicate | transferBasis |
P193304
|
FINISHED |
| Object | Treaty of Saint-Germain-en-Laye |
—
|
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 Saint-Germain-en-Laye | Statement: [Kittsee, transferBasis, Treaty of Saint-Germain-en-Laye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferBasis Context triple: [Kittsee, transferBasis, Treaty of Saint-Germain-en-Laye]
-
A.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
-
B.
transferBetween
Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
-
C.
transferPrice
Indicates a relationship where a price is assigned or paid to transfer ownership or control of something from one party to another.
-
D.
transferFeature
Indicates a relationship where a feature, attribute, or capability is moved or reassigned from one entity to another.
-
E.
transferAgreement
Indicates a formal arrangement in which ownership, rights, or responsibilities are transferred from one party to another.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: April 28, 2026, 9:58 a.m.