Triple
T36438049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikorsky VS-300 |
E897644
|
entity |
| Predicate | configurationBecameStandardFor |
P27075
|
FINISHED |
| Object | most modern helicopters |
—
|
LITERAL 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: most modern helicopters | Statement: [Sikorsky VS-300, configurationBecameStandardFor, most modern helicopters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationBecameStandardFor Context triple: [Sikorsky VS-300, configurationBecameStandardFor, most modern helicopters]
-
A.
becameStandardFor
chosen
Indicates that something was adopted and established as the usual or accepted norm for a particular purpose, context, or group.
-
B.
implementedAsStandardBy
Indicates that a standard is put into practice or realized through implementation by a specific entity (such as an organization, system, or component).
-
C.
becameStandardIn
Indicates that something was adopted and recognized as the standard within a particular context, domain, or time period.
-
D.
revisedByStandard
Indicates that something has been updated or modified in accordance with a specified standard or set of standards.
-
E.
replacedStandard
Indicates that one standard has been superseded or taken the place of another standard.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.