Triple
T23008962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TMA-10 |
E572854
|
entity |
| Predicate | dockingPort |
P14974
|
FINISHED |
| Object | Pirs module |
—
|
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: Pirs module | Statement: [Soyuz TMA-10, dockingPort, Pirs module]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pirs module Context triple: [Soyuz TMA-10, dockingPort, Pirs module]
-
A.
Pirs
chosen
Pirs was a Russian docking compartment and airlock module on the International Space Station used for spacecraft docking and spacewalks.
-
B.
PIR
PIR is the commonly used acronym for Portland International Raceway, a motorsports and event venue in Portland, Oregon.
-
C.
PIR
PIR is the vehicle registration code used on license plates for vehicles registered in the town of Pirna in Germany.
-
D.
PIR
PIR is the former stock ticker symbol for Pier 1 Imports, a U.S.-based retailer known for its imported home furnishings and décor.
-
E.
PIR
PIR is a popular abbreviation for Phoenix Raceway, a major motorsports venue in Avondale, Arizona known for hosting NASCAR and other racing events.
- F. None of above.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1835919b08190ba78e182b87358d4 |
completed | April 29, 2026, 4:04 a.m. |
Created at: April 17, 2026, 3:51 p.m.