Triple
T34980968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glienicke Bridge prisoner exchange |
E1008811
|
entity |
| Predicate | notableExchangeSiteFor |
P149636
|
FINISHED |
| Object | U.S.–Soviet spy swaps |
E1008810
|
NE 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: U.S.–Soviet spy swaps | Statement: [Glienicke Bridge prisoner exchange, notableExchangeSiteFor, U.S.–Soviet spy swaps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableExchangeSiteFor Context triple: [Glienicke Bridge prisoner exchange, notableExchangeSiteFor, U.S.–Soviet spy swaps]
-
A.
notableExchange
Indicates a significant or noteworthy transfer, interaction, or trade occurring between two or more entities.
-
B.
notableSiteFor
chosen
Indicates that a site is particularly recognized or distinguished for a specific feature, activity, event, or characteristic.
-
C.
notableSite
Indicates that a site holds particular significance, prominence, or recognition in some context.
-
D.
exchanges
Indicates a reciprocal transfer of something of value between two or more entities.
-
E.
notableSiteListedOn
Indicates that a notable site is recorded or referenced within a particular list, registry, or catalog.
- F. None of above.
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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b27fc0dc8190b1c1976265e06314 |
completed | June 21, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.