Triple
T23528863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TMA-14 |
E576506
|
entity |
| Predicate | callsign |
P1565
|
FINISHED |
| Object | Olymp |
—
|
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: Olymp | Statement: [Soyuz TMA-14, callsign, Olymp]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Olymp Context triple: [Soyuz TMA-14, callsign, Olymp]
-
A.
Olympiada
Olympiada is a coastal village in northern Greece known for its proximity to the ancient city of Stagira, birthplace of the philosopher Aristotle.
-
B.
Olimp
Olimp is a seaside resort town on Romania’s Black Sea coast, known for its beaches and holiday accommodations.
-
C.
Kolympia
Kolympia is a coastal village and holiday resort on the island of Rhodes in Greece, known for its beaches and tourist facilities.
-
D.
Olympoi
Olympoi is a well-preserved medieval mastic-growing village on the Greek island of Chios, known for its fortified architecture and narrow stone alleys.
-
E.
Olympiasee
Olympiasee is an artificial lake in Munich’s Olympic Park, created for the 1972 Summer Olympics and now a popular recreational and scenic spot.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac758038819098f5f597be39274e |
completed | April 29, 2026, 7 a.m. |
Created at: April 17, 2026, 6:09 p.m.