Triple
T18813173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikorsky H-5 |
E460066
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | R-5 |
—
|
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: R-5 | Statement: [Sikorsky H-5, alsoKnownAs, R-5]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: R-5 Context triple: [Sikorsky H-5, alsoKnownAs, R-5]
-
A.
R-5
chosen
The R-5 is an early Sikorsky military helicopter developed during World War II, known for advancing rotary-wing design and serving in roles such as rescue and liaison.
-
B.
R-11
R-11 is a Soviet short-range tactical ballistic missile that formed the basis for the later Scud missile family.
-
C.
R5
R5 is the common shorthand name for the Renault 5, a popular compact hatchback car produced by the French manufacturer Renault.
-
D.
R5
R5 is the U.S. Forest Service’s Pacific Southwest Region, which oversees national forests primarily in California and parts of neighboring areas.
-
E.
R5
R5 was a former designation for a commuter rail line in the SEPTA Regional Rail system serving the Paoli/Thorndale corridor in the Philadelphia area.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3de2f6881908a9da4d5abd7ee61 |
completed | April 20, 2026, 3:56 a.m. |
Created at: April 10, 2026, 11:53 a.m.