Triple
T6121631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-76 |
E136497
|
entity |
| Predicate | spaceStationVisited |
P21539
|
FINISHED |
| Object | Mir |
E118091
|
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: Mir | Statement: [STS-76, spaceStationVisited, Mir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mir Context triple: [STS-76, spaceStationVisited, Mir]
-
A.
Mir
chosen
Mir was a Soviet and later Russian modular space station that served as a long-term research outpost in low Earth orbit from 1986 to 2001.
-
B.
Mir
Mir is a traditional South Asian noble title historically used by rulers and aristocrats, particularly in regions such as Sindh under dynasties like the Talpurs.
-
C.
Mari
Mari is a Uralic language spoken by the Mari people, primarily in the Mari El Republic of Russia.
-
D.
Mari
Mari is a character in Paulo Coelho's novel "Veronika Decides to Die," portrayed as a fellow patient in the mental institution who struggles with anxiety and societal expectations.
-
E.
Mari
Mari is a feminine given name, often used as a short form of names like Marigold, Mary, or Maria in various cultures.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bf16ad48190958cc46510e02bd3 |
completed | March 22, 2026, 9:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c135a5c428819090066ad785296736 |
completed | March 23, 2026, 12:44 p.m. |
Created at: March 22, 2026, 4:14 p.m.