Triple
T38148423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UH-34 |
E952683
|
entity |
| Predicate | navalVariantOf |
P73519
|
FINISHED |
| Object | Sikorsky H-34 |
—
|
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: Sikorsky H-34 | Statement: [UH-34, navalVariantOf, Sikorsky H-34]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalVariantOf Context triple: [UH-34, navalVariantOf, Sikorsky H-34]
-
A.
maritimeVariant
chosen
Indicates a version or form of something that is specifically adapted for or used in maritime (sea-related) contexts.
-
B.
navalName
Indicates that an entity has a specific name used in a naval or maritime context.
-
C.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
-
D.
navalTechnologyType
Indicates the specific category or type of naval technology associated with an entity.
-
E.
navalAnalogue
Indicates that one entity serves as the naval or maritime counterpart or equivalent of another entity in function, role, or classification.
- F. None of above.
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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.