Triple
T10823045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-19 Chickasaw |
E255422
|
entity |
| Predicate | civilDesignation |
P974
|
FINISHED |
| Object | Sikorsky S-55 |
E460066
|
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: Sikorsky S-55 | Statement: [H-19 Chickasaw, civilDesignation, Sikorsky S-55]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sikorsky S-55 Context triple: [H-19 Chickasaw, civilDesignation, Sikorsky S-55]
-
A.
Sikorsky V
Sikorsky V is a designated satellite crater on the Moon associated with the larger Sikorsky impact crater.
-
B.
Sikorsky X
Sikorsky X is a designated satellite impact crater located on the Moon near the main Sikorsky crater.
-
C.
Sikorsky H-5 helicopter
chosen
The Sikorsky H-5 is an early post–World War II American utility and rescue helicopter that played a key role in pioneering rotary-wing military and search-and-rescue operations.
-
D.
Sikorsky Q
Sikorsky Q is a designated satellite crater on the Moon associated with the larger lunar impact feature Sikorsky.
-
E.
Sikorsky Z
Sikorsky Z is a small lunar satellite crater located near the larger Sikorsky crater on the far side of the Moon.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344c551c8190a7491d468b8a4a04 |
completed | April 9, 2026, 5:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e21649a6308190878432635d523686 |
completed | April 17, 2026, 11:15 a.m. |
Created at: April 8, 2026, 9:19 p.m.